| 2 |
Approval of Agenda |
|
| R1-2310780 |
Draft Agenda of RAN1#115 meeting |
RAN1 Chair |
| R1-2310782 |
RAN1#115 Meeting Timelines, Scope, Process |
ETSI MCC |
| R1-2310783 |
RAN1#115 Meeting Management |
RAN1 Chair |
| 4 |
Approval of Minutes from previous meetings |
|
| R1-2310781 |
Report of RAN1#114bis meeting |
ETSI MCC |
| 5 |
Incoming Liaison Statements |
|
| R1-2310784 |
LS to RAN1 on RAN2 progress of NTN Self Evaluation |
RAN2, Ericsson |
| R1-2310785 |
LS on extended PRS and SRS periodicity |
RAN2, Huawei |
| R1-2310786 |
Reply LS on the resource selection window for Scheme 2 in a dedicated resource pool for positioning |
RAN2, Qualcomm |
| R1-2310787 |
LS on request for clarifications on RedCap positioning, carrier phase positioning, and bandwidth aggregation for positioning |
RAN2, Nokia |
| R1-2310788 |
LS on UE Capability of Multicast Reception in RRC_INACTIVE |
RAN2, vivo |
| R1-2310789 |
Reply LS on R1-2308644 for CPP |
RAN2, CATT |
| R1-2310790 |
LS on TA validation for LPHAP |
RAN2, Huawei |
| R1-2310791 |
LS on extended CG-SDT periodicities |
RAN2, Ericsson |
| R1-2310792 |
Reply LS on monitoring of paging occasions for CG-SDT with HD-FDD Redcap UEs |
RAN2, MediaTek |
| R1-2310793 |
LS reply to RAN4 LS R4-2314351 |
RAN2, Ericsson |
| R1-2310794 |
Reply LS on required DCI signalling for advanced receiver on MU-MIMO scenario |
RAN4, HiSilicon, Apple, China Telecom |
| R1-2310795 |
Reply LS on beam application time for LTM |
RAN4, Ericsson |
| R1-2310796 |
Reply LS on determination of UL timing to transmit SRS for positioning by UEs in RRC_INACTIVE states |
RAN4, CMCC |
| R1-2310797 |
Reply LS to RAN1 on SRS and PRS bandwidth aggregation for positioning |
RAN4, ZTE Corporation |
| R1-2310798 |
LS on SL positioning and carrier phase positioning measurements |
RAN4, CATT |
| R1-2310799 |
LS on conclusions on BWP operation without restriction |
RAN4, vivo, Vodafone |
| R1-2310800 |
LS reply on further clarifications on enhancements to realize increasing UE power high limit for CA and DC |
RAN4, Huawei |
| R1-2310801 |
LS on network assistant signalling for advanced receivers |
RAN4, Nokia |
| R1-2310802 |
LS on SSB-less operation for Rel-18 NES |
RAN4, Huawei |
| R1-2310803 |
LS on report mapping for positioning measurements with PRS_SRS bandwidth aggregation |
RAN4, Ericsson |
| R1-2310804 |
LS on Rel-18 UL Tx switching for parallel switching on four bands |
RAN4, MediaTek |
| R1-2310805 |
LS on unaffected band case for UL Tx switching |
RAN4, vivo |
| R1-2310806 |
LS on a capability of UE power class and IE on PEMAX,CA for SL CA |
RAN4, LG Electronics, OPPO |
| R1-2310807 |
LS on Rel-18 Tx switching enhancement |
RAN4, Huawei |
| R1-2310808 |
LS on AI/ML Core Network enhancements |
SA2, Qualcomm |
| R1-2310809 |
LS on L1 measurements for LTM |
RAN2, Ericsson |
| R1-2310810 |
Reply LS to SA2 on reporting positioning measurements taken in RRC_IDLE |
RAN2, CATT |
| R1-2310833 |
Discussion on simultaneous reception for Rel-18 MBS |
Huawei, HiSilicon, CBN |
| R1-2310876 |
Further discussion on LS for RACH-less handover |
Huawei, HiSilicon |
| R1-2310905 |
Discussion of SA2 LS on AI/ML Core Network Enhancements |
Ericsson |
| R1-2310909 |
Discussion on RAN4 LS on required DCI signalling for advanced MU-MIMO receiver |
Ericsson |
| R1-2310958 |
Discussion on required DCI signalling for advanced receiver on MU-MIMO scenario |
ZTE |
| R1-2310959 |
Discussion on L1 measurements for LTM |
ZTE |
| R1-2310964 |
LS on NAS Cause Value - Unspecified |
SA3-LI, Tridea Works |
| R1-2310975 |
Discussion on LS on L1 measurements |
Ericsson |
| R1-2310976 |
Discussion on LS on MIMOevo |
Ericsson |
| R1-2310982 |
Draft Reply LS on request for clarifications on RedCap positioning, carrier phase positioning, and bandwidth aggregation for positioning |
Nokia, Nokia Shanghai Bell |
| R1-2311001 |
LS on Stage-2 CR for MIMO evolution |
RAN2, NTT DOCOMO |
| R1-2311002 |
LS on NES CHO |
RAN2, Apple |
| R1-2311003 |
Reply LS on Priority Handling for SL Positioning |
RAN2, Intel Corporation |
| R1-2311004 |
LS on MIMOevo |
RAN2, Ericsson |
| R1-2311005 |
LS to RAN1 on PHR reporting |
RAN2, InterDigital |
| R1-2311006 |
Reply LS on delta power class |
RAN2, Nokia |
| R1-2311007 |
[Draft] Reply LS on UE Capability of Multicast Reception in RRC_INACTIVE |
ZTE, CBN |
| R1-2311008 |
Discussion on multicast reception in RRC_INACTIVE |
ZTE, CBN |
| R1-2311055 |
Discussion on beam application time for L1/L2-Triggered Mobility |
vivo |
| R1-2311056 |
Draft reply LS on L1 measurements for LTM |
vivo |
| R1-2311057 |
Discussion on required DCI signalling for advanced receiver on MU-MIMO scenario |
vivo |
| R1-2311058 |
Discussion on collision handling between paging occasions and CG SDT for HD-FDD Ues |
vivo |
| R1-2311059 |
Draft reply LS on monitoring of paging occasions for CG-SDT with HD-FDD Redcap Ues |
vivo |
| R1-2311060 |
Discussion of LS on extended CG-SDT periodicities |
vivo |
| R1-2311061 |
Draft reply LS on clarifications on RedCap positioning, carrier phase positioning, and bandwidth aggregation for positioning |
vivo |
| R1-2311062 |
Draft reply LS on CPP related issues |
vivo |
| R1-2311063 |
Discussion on reply LS to SA2 on AI/ML Core Network enhancements |
vivo |
| R1-2311064 |
Discussions on RAN2 LS on RACH-less Handover |
vivo |
| R1-2311065 |
Discussion of the LS on the system parameters for NTN above 10 GHz |
vivo |
| R1-2311066 |
Draft reply LS on UE Capability of Multicast Reception in RRC_INACTIVE |
vivo |
| R1-2311067 |
Draft TPs for UE supporting FDMed multicast MCCH and PBCH in a slot for multicast reception in RRC_INACTIVE |
vivo |
| R1-2311068 |
Draft reply LS to RAN2 on PHR reporting |
vivo |
| R1-2311069 |
Draft reply LS on Stage-2 CR for MIMO evolution |
vivo |
| R1-2311070 |
Draft reply LS on MIMOevo |
vivo |
| R1-2311071 |
Draft reply LS on NES CHO |
vivo |
| R1-2311130 |
Draft Reply LS on clarification on Carrier Phase Positioning |
Nokia, Nokia Shanghai Bell |
| R1-2311131 |
Discussion on LS for extended CG-SDT periodicities for SDT operation |
Intel Corporation |
| R1-2311132 |
DRAFT Reply LS on request for clarifications on RedCap positioning, carrier phase positioning, and bandwidth aggregation for positioning |
Intel Corporation |
| R1-2311133 |
DRAFT Reply LS on RAN2 questions for CPP |
Intel Corporation |
| R1-2311153 |
Discussion on LS on request for clarifications on RedCap positioning, carrier phase positioning, and bandwidth aggregation for positioning |
Spreadtrum Communications |
| R1-2311154 |
Discussion on Reply LS on R1-2308644 for CPP |
Spreadtrum Communications |
| R1-2311195 |
Discussion on LS on longer CG-SDT periodicities |
ZTE |
| R1-2311209 |
Draft reply LS to RAN2 on Stage-2 CR for MIMO evolution |
ZTE |
| R1-2311210 |
Draft reply LS to RAN2 on MIMOevo |
ZTE |
| R1-2311211 |
Discussion on RAN2 LS on RACH-less Handover |
ZTE |
| R1-2311222 |
Discussion on LS on Stage-2 CR for MIMO evolution |
OPPO |
| R1-2311223 |
Discussion on LS on RRC parameters for MIMOevo |
OPPO |
| R1-2311228 |
Discussion on request for clarifications on carrier phase positioning and bandwidth aggregation for positioning |
OPPO |
| R1-2311229 |
Discussion on request for clarifications on RedCap UE positioning |
OPPO |
| R1-2311233 |
Discussion on LS on L1 measurements for LTM |
OPPO |
| R1-2311234 |
Discussion on Reply LS on beam application time for LTM |
OPPO |
| R1-2311249 |
Discussion on remaining issue for RACH less handover for NR NTN |
OPPO |
| R1-2311250 |
Discussion on remaining issue for FR2-NTN |
OPPO |
| R1-2311251 |
Discussion on LS on NES CHO |
OPPO |
| R1-2311252 |
Draft reply LS on NES CHO |
OPPO |
| R1-2311260 |
Discussion on RAN2 LS on NTN Self Evaluation |
OPPO |
| R1-2311261 |
Draft reply LS on NTN Self Evaluation |
OPPO |
| R1-2311268 |
Discussion on reply LS for UE reporting PCMAX for actual and assumed PUSCH |
OPPO |
| R1-2311272 |
Discussion on SA2 LS “LS on AI/ML Core Network enhancements” |
OPPO |
| R1-2311281 |
Discussion on RAN2 LS on RACH-less handover |
Ericsson |
| R1-2311283 |
Discussion on RAN2 LS on UE capability for multicast reception in RRC_INACTIVE |
CATT, CBN |
| R1-2311284 |
Discussions on RAN2 LS on RACH-less Handover |
CATT |
| R1-2311285 |
Discussion on request for clarifications on RedCap positioning, carrier phase positioning, and bandwidth aggregation for positioning |
CATT |
| R1-2311286 |
Draft reply LS on request for clarifications on RedCap positioning, carrier phase positioning, and bandwidth aggregation for positioning |
CATT |
| R1-2311287 |
Discussion on RAN2 LS on CPP |
CATT |
| R1-2311288 |
Draft reply LS on R2-2311565 for CPP |
CATT |
| R1-2311313 |
Discussion on reply LS to SA2 on AI/ML Core Network enhancements |
CATT |
| R1-2311370 |
Draft reply LS on L1 measurements for LTM |
Lenovo |
| R1-2311371 |
Draft Reply LS on Stage-2 CR for MIMO evolution |
Lenovo |
| R1-2311372 |
Draft Reply LS on MIMOevo |
Lenovo |
| R1-2311373 |
Draft reply LS on MIMOevo |
CATT |
| R1-2311375 |
Draft reply LS for CPP |
xiaomi |
| R1-2311376 |
Draft reply LS for clarifications on RedCap positioning, carrier phase positioning and bandwidth aggregation for positioning |
xiaomi |
| R1-2311377 |
Discussion on SA LS on AI/ML Core Network enhancements |
xiaomi |
| R1-2311378 |
Discussion on extended CG-SDT periodicities |
xiaomi |
| R1-2311424 |
Discussion the impact of longer CG-SDT periodicities |
NEC |
| R1-2311451 |
Discussion on NES CHO |
ZTE, Sanechips |
| R1-2311452 |
Draft reply LS for CPP |
ZTE |
| R1-2311453 |
Discussion on CPP issues for RAN2 reply LS R1-2310789 |
ZTE |
| R1-2311454 |
Draft reply LS on clarifications for RedCap positioning, carrier phase positioning, and bandwidth aggregation for positioning |
ZTE |
| R1-2311455 |
Discussion on issues of CPP and bandwidth aggregation positioning for RAN2 LS R1-2310787 |
ZTE |
| R1-2311467 |
Discussion on multicast reception in RRC_INACTIVE |
CMCC |
| R1-2311468 |
Discussion on LS on UE Capability of Multicast Reception in RRC_INACTIVE |
CMCC |
| R1-2311469 |
Discussion on signaling design for CHO enhancement in DCI format 2_9 |
CMCC |
| R1-2311470 |
Discussion on the LS on L1 measurement for LTM |
CMCC |
| R1-2311471 |
Discussion on RAN2 LS for clarifications on positioning |
CMCC |
| R1-2311507 |
Discussion on reply LS on paging overlapping with CG-SDT for HD-FDD RedCap UE |
ZTE |
| R1-2311508 |
Draft reply LS on paging and CG-SDT conflicting issue for HD-FDD RedCap UE |
ZTE |
| R1-2311524 |
Discussion on LS on Stage-2 CR for MIMO evolution |
Ericsson |
| R1-2311531 |
Draft Reply LS on PHR reporting |
InterDigital, Inc. |
| R1-2311542 |
Discussion on RAN4 Reply LS of advanced receiver for MU-MIMO |
China Telecom |
| R1-2311543 |
Discussion on RAN2 Reply LS of reporting PCMAX for assumed PUSCH transmissions in CA/DC scenario |
China Telecom |
| R1-2311561 |
Discussion of SA2 LS on AI/ML Core Network Enhancements |
ZTE |
| R1-2311584 |
Draft Reply LS on MIMO Evolution |
Google |
| R1-2311594 |
Discussion on LS reply for clarifications on RedCap positioning, carrier phase positioning, and bandwidth aggregation for positioning |
InterDigital, Inc. |
| R1-2311603 |
Draft reply LS on Stage-2 CR for MIMO evolution |
NTT DOCOMO, INC. |
| R1-2311604 |
Discussion on reply LS on request for clarifications on RedCap positioning, carrier phase positioning, and bandwidth aggregation for positioning |
NTT DOCOMO, INC. |
| R1-2311605 |
Discussion on reply LS on RAN2 questions about RSCP/RSCPD |
NTT DOCOMO, INC. |
| R1-2311606 |
Discussion on LS from SA2 on Rel-18 AI/ML for air interface |
NTT DOCOMO, INC. |
| R1-2311658 |
Draft reply LS on UE Capability of Multicast Reception in RRC_INACTIVE |
Apple |
| R1-2311659 |
Maintenance of multicast reception in RRC_INACTIVE |
Apple |
| R1-2311660 |
[Draft] Reply LS on L1 measurements for LTM |
Apple |
| R1-2311661 |
Discussion on RAN2 LS on L1 measurements for LTM |
Apple |
| R1-2311662 |
Discussion on RAN2 LS on extended CG-SDT periodicities |
Apple |
| R1-2311663 |
Discussion on RAN2 LS on NES CHO |
Apple |
| R1-2311664 |
Discussion on RAN2 LS on RACH-less Handover |
Apple |
| R1-2311665 |
Reply LS on requirement for SA2 to support AI/ML for air interface |
Apple |
| R1-2311722 |
Draft Reply LS on PHR reporting |
Lenovo |
| R1-2311729 |
Extended CG-SDT periodicities introduction to TS38.213 |
Nokia, Nokia Shanghai Bell |
| R1-2311736 |
Discussion on the LS reply on Stage-2 CR for MIMO evolution |
Nokia, Nokia Shanghai Bell |
| R1-2311737 |
Draft LS reply on Stage-2 CR for MIMO evolution |
Nokia, Nokia Shanghai Bell |
| R1-2311738 |
Draft LS reply on MIMOevo |
Nokia, Nokia Shanghai Bell |
| R1-2311777 |
Discussion on Rel-18 UL Tx switching for parallel switching on four bands |
ZTE |
| R1-2311787 |
Discussion on multicast reception in RRC_INACTIVE |
Nokia, Nokia Shanghai Bell |
| R1-2311788 |
[Draft] Reply LS on UE Capability of Multicast Reception in RRC_INACTIVE |
Nokia, Nokia Shanghai Bell |
| R1-2311800 |
Discussion on LS on NES CHO |
Nokia, Nokia Shanghai Bell |
| R1-2311801 |
Draft reply LS on NES CHO |
Nokia, Nokia Shanghai Bell |
| R1-2311802 |
Draft reply LS on MIMOevo |
Samsung |
| R1-2311803 |
Discussion on RAN4 LS on required DCI signalling for advanced receiver on MU-MIMO scenario |
Samsung |
| R1-2311804 |
Discussion on report quantity parameter setting for CQI reporting with 1Tx |
Samsung |
| R1-2311805 |
Discussion on RAN2 LS on RACH-less handover |
Samsung |
| R1-2311806 |
Discussion on RAN4 LS on system parameters for NTN above 10 GHz |
Samsung |
| R1-2311807 |
Draft reply LS on L1 measurements for LTM |
Samsung |
| R1-2311808 |
Draft reply LS on request for clarifications on RedCap positioning, carrier phase positioning, and bandwidth aggregation for positioning |
Samsung |
| R1-2311809 |
Draft reply LS on CPP |
Samsung |
| R1-2311810 |
Discussion on SA2's LS on AI/ML Core Network enhancements |
Samsung |
| R1-2311811 |
Draft reply LS on UE Capability of FDMed between Multicast MCCH and PBCH |
Samsung |
| R1-2311812 |
Draft reply LS on PHR reporting |
Samsung |
| R1-2311813 |
Draft reply LS on Stage-2 CR for MIMO evolution |
Samsung |
| R1-2311820 |
Draft CR on SSB to CG PUSCH mapping in CG-SDT |
Samsung |
| R1-2311821 |
Discussion on SSB to CG PUSCH mapping in CG-SDT |
Samsung |
| R1-2311891 |
Draft Reply LS on L1 Measurements for LTM |
Nokia, Nokia Shanghai Bell |
| R1-2311892 |
Discussion on Reply LS on Beam Application Time for LTM |
Nokia, Nokia Shanghai Bell |
| R1-2311914 |
Discussion on RAN2 LS on DWS MAC CE for reporting PHR in CA/DC |
LG Electronics |
| R1-2311923 |
Draft reply LS on RAN1 impacts concerning PHR reporting for actual and assumed PUSCH for coverage enhancement |
Nokia, Nokia Shanghai Bell |
| R1-2311924 |
Draft reply LS on RAN1 impacts concerning enhancements to realize increasing UE power high limit for CA and DC for coverage enhancement |
Nokia, Nokia Shanghai Bell |
| R1-2311937 |
Discussion on RAN2 LS on NES CHO |
Lenovo |
| R1-2311956 |
Discussion on RAN4 reply LS on DCI for MU-MIMO advanced receiver |
MediaTek Inc. |
| R1-2311957 |
Draft LS reply on UE Capability of Multicast Reception in RRC_INACTIVE |
MediaTek Inc. |
| R1-2311958 |
Draft reply LS on MIMOevo |
MediaTek Inc. |
| R1-2311959 |
Discussion on RAN2 LS on extended CG-SDT periodicities |
MediaTek Inc. |
| R1-2312011 |
Discussion on the RAN1 spec impact to support multicast reception in RRC_INACTIVE |
Qualcomm Incorporated |
| R1-2312012 |
Discussion of RAN2 LS on the UE Capability of Multicast Reception in RRC_INACTIVE |
Qualcomm Incorporated |
| R1-2312013 |
Discussion of SA2 LS on AI/ML Core Network enhancements |
Qualcomm Incorporated |
| R1-2312096 |
Discussion related to RAN4 LS on inter-band SSB-less SCell |
Ericsson |
| R1-2312108 |
TP for TS 38.300 regarding 8Tx UL |
ASUSTeK |
| R1-2312110 |
Impact on DCI format_2_9 regarding NES-specific CHO |
ASUSTeK |
| R1-2312114 |
Discussion on LS on NES CHO |
FGI |
| R1-2312116 |
Draft reply LS on PHR reporting for dynamic waveform switching |
ZTE |
| R1-2312130 |
Discussion on LS on request for clarifications on RedCap positioning, carrier phase positioning, and bandwidth aggregation for positioning |
LG Electronics |
| R1-2312131 |
Discussion on Reply LS on R1-2308644 for CPP |
LG Electronics |
| R1-2312145 |
Discussion on additional k values for BW aggregation |
Huawei, HiSilicon |
| R1-2312146 |
Discussion on PRS/SRS periodicity larger than 10.24s |
Huawei, HiSilicon |
| R1-2312147 |
Discussion on RAN2 LS for CPP |
Huawei, HiSilicon |
| R1-2312148 |
Discussion on RAN4 LS on a capability of UE power class and IE on PEMAX,CA for SL CA |
Huawei, HiSilicon |
| R1-2312154 |
Discussion on longer CG-SDT periodicities |
Huawei, HiSilicon |
| R1-2312156 |
Discussion on LS on NES CHO |
Huawei, HiSilicon |
| R1-2312163 |
Monitoring of paging occasions for CG-SDT with HD-FDD RedCap UEs |
Ericsson |
| R1-2312164 |
On extended CG-SDT periodicities |
Ericsson |
| R1-2312165 |
Introduction of extended CG-SDT periodicities |
Ericsson |
| R1-2312176 |
Discussions on RAN2 LS on RACH-less Handover |
CATT |
| R1-2312182 |
Discussion on LS on extended PRS and SRS periodicity |
Ericsson |
| R1-2312183 |
Discussion on LS on request for clarifications on RedCap |
Ericsson |
| R1-2312184 |
Discussion on Reply LS for CPP |
Ericsson |
| R1-2312193 |
Discussion on LS on UE capability of multicast reception in RRC_INACTIVE |
Ericsson |
| R1-2312197 |
Draft reply LS on RAN1 impacts of enhancements to realize increasing UE power high limit for CA and DC |
Ericsson |
| R1-2312198 |
Draft Reply LS on RAN1 impacts of PHR reporting for DC/CA scenario |
Ericsson |
| R1-2312199 |
DCI signalling for advanced receiver on MU-MIMO scenario |
Nokia, Nokia Shanghai Bell |
| R1-2312207 |
Text proposal for Rel-18 MBS |
Huawei, HiSilicon, CBN |
| R1-2312208 |
Text proposal for Rel-18 MBS to TS38.211 |
Huawei, HiSilicon, CBN |
| R1-2312209 |
Text proposal for Rel-18 MBS to TS38.212 |
Huawei, HiSilicon, CBN |
| R1-2312210 |
Text proposal for Rel-18 MBS to TS38.213 |
Huawei, HiSilicon, CBN |
| R1-2312211 |
Text proposal for Rel-18 MBS to TS38.214 |
Huawei, HiSilicon, CBN |
| R1-2312213 |
Discussion on RSCP/RSCPD quality |
Huawei, HiSilicon |
| R1-2312216 |
Discussion on SL positioning MAC agreements |
Huawei, HiSilicon |
| R1-2312223 |
Discussion on the RAN2 LS on L1 measurements for LTM |
Huawei, HiSilicon |
| R1-2312229 |
Discussion on LS reply to SA2 on air interface AI/ML |
Huawei, HiSilicon |
| R1-2312230 |
Discussion on request for clarifications on RedCap positioning, carrier phase positioning, and bandwidth aggregation for positioning |
Huawei, HiSilicon |
| R1-2312231 |
Discussion on PHR reporting of CA/DC for Rel-18 dynamic waveform switching |
Huawei, HiSilicon |
| R1-2312237 |
Discussion of LS on Stage-2 CR for MIMO evolution |
Huawei, HiSilicon |
| R1-2312238 |
Discussion of LS on MIMOevo RRC parameters |
Huawei, HiSilicon |
| R1-2312239 |
Discussion on required DCI signalling for advanced receiver on MU-MIMO scenario |
Huawei, HiSilicon |
| R1-2312340 |
Moderator summary #1 of discussion of Reply LS on required DCI signalling for advanced receiver on MU-MIMO scenario |
Moderator (Qualcomm) |
| R1-2312427 |
Summary of TPs for multicast reception in RRC_INACTIVE |
Moderator (Apple) |
| R1-2312448 |
Moderator summary for LS on extended CG-SDT periodicities |
Moderator (Ericsson) |
| R1-2312449 |
Introduction of extended CG-SDT periodicities |
Moderator (Ericsson), ZTE, Samsung, Ericsson |
| R1-2312494 |
LS on Sidelink CSI Reporting MAC-CE for SL-CA |
RAN2, OPPO |
| R1-2312497 |
Summary on replying LS on UE Capability of Multicast Reception in RRC_INACTIVE |
Moderator (vivo) |
| R1-2312534 |
Moderator summary#2 for LS on extended CG-SDT periodicities |
Moderator (Ericsson) |
| R1-2312641 |
Reply LS on UE Capability of Multicast Reception in RRC_INACTIVE |
RAN1, vivo |
| R1-2312658 |
Introduction of extended CG-SDT periodicities [CG-SDT-Enh] |
Moderator (Ericsson), ZTE, Samsung, xiaomi, Ericsson |
| R1-2312765 |
RAN2 input to TR 38.843 |
RAN2, Ericsson |
| 6 |
Pre-Rel-18 E-UTRA Maintenance |
|
| R1-2312014 |
Correction on Koffset during random access procedure |
Qualcomm Incorporated |
| R1-2312308 |
Correction on Koffset during random access procedure |
Qualcomm Incorporated |
| R1-2312390 |
Discussion on R1-2312308 - Correction on Koffset during random access procedure |
Moderator (Qualcomm Incorporated) |
| R1-2312490 |
Correction on Koffset during random access procedure |
Qualcomm Incorporated |
| R1-2312491 |
Correction on Koffset during random access procedure |
Qualcomm Incorporated |
| R1-2312568 |
Session notes for 6 (Pre-Rel-18 E-UTRA Maintenance) |
Ad-Hoc Chair (Huawei) |
| 7.1 |
Maintenance on NR Releases 15 – 16 |
|
| R1-2310872 |
Correction on CSI reporting for 1 CSI-RS port |
Huawei, HiSilicon |
| R1-2310912 |
Discussion on issues with type 2 CG-PUSCH |
Ericsson |
| R1-2310918 |
Correction on collision between NR PDSCH DMRS and LTE-CRS |
Huawei, HiSilicon |
| R1-2310929 |
Correction for SRS carrier switching for DCI formats 1_1 and 1_2 |
Ericsson, T-Mobile USA, Verizon |
| R1-2310943 |
Draft CR correcting power allocation reference in 38.211 |
Ericsson |
| R1-2310944 |
Draft CR correcting power allocation reference in 38.211 |
Ericsson |
| R1-2310960 |
Discussion on aperiodic triggering support for SRS carrier switching |
ZTE |
| R1-2310961 |
Draft CR on CQI reporting with 1Tx on PUSCH in TS 38.212 |
ZTE |
| R1-2310962 |
Discussion on SCell Type 1 virtual PHR reporting in UL CA |
ZTE |
| R1-2311009 |
Discussion of scheduling restriction for FDD-TDD UL CA |
ZTE |
| R1-2311010 |
Discussion of SUL indicator in case pucch-Config not configured |
ZTE |
| R1-2311011 |
Discussion on several ambiguities with type 2 CG PUSCH |
ZTE |
| R1-2311012 |
Discussion on CSI multiplexing behavior when multi-CSI-PUCCH-ResourceList is not provided |
ZTE |
| R1-2311039 |
Discussion on aperiodic triggering of SRS carrier switching |
Fujitsu |
| R1-2311072 |
Discussion on SRS transmission occasion |
vivo |
| R1-2311073 |
Clarifying several ambiguities with type 2 CG-PUSCH |
vivo |
| R1-2311074 |
Discussion on scheduling issue for TDD-FDD UL CA |
vivo |
| R1-2311075 |
Draft CR on PUSCH selection rule for UCI multiplexing |
vivo |
| R1-2311076 |
Discussion on PUSCH selection rule for UCI multiplexing |
vivo |
| R1-2311221 |
Discussion on aperiodic triggering support for SRS carrier switching |
OPPO |
| R1-2311289 |
Clarification on the first SPS PDSCH and Type2 CG PUSCH |
CATT, Apple |
| R1-2311290 |
Correction on fallback Type-1 HARQ-ACK codebook |
CATT |
| R1-2311291 |
Correction on fallback Type-1 HARQ-ACK codebook |
CATT |
| R1-2311360 |
On the collision between NR PDSCH DMRS and LTE-CRS |
Ericsson |
| R1-2311448 |
Correction on PHR reporting for overlapping PUSCHs |
CATT |
| R1-2311578 |
Discussion on default pathloss reference signal for SRS and PUCCH |
Google |
| R1-2311579 |
Draft CR on default pathloss reference signal for SRS and PUCCH |
Google |
| R1-2311602 |
HARQ-ACK feedback enhancements for CA |
CATT, CMCC |
| R1-2311666 |
On triggering A-SRS for carrier-based switching by a UE specific DCI |
Apple |
| R1-2311667 |
Remaining ambiguity issues on the 1st Type-2 CG PUSCH |
Apple |
| R1-2311668 |
Discussion on PUSCH with repetitions or multi-PUSCHs with an UL DAI |
Apple |
| R1-2311669 |
Discussion on UCI processing for the first SPS PDSCH |
Apple |
| R1-2311670 |
On memory issues associated to slot offset determination for A-CSI on PUSCH without data |
Apple |
| R1-2311671 |
Clarification of serving cell index in CSI priority calculation |
Apple |
| R1-2311672 |
Clarification of slot offset calculation for PUSCH carrying aperiodic CSI with no transport block |
Apple, Nokia, Nokia Shanghai Bell, Ericsson |
| R1-2311730 |
On SCell Type 1 virtual PHR reporting in UL CA |
Nokia, Nokia Shanghai Bell |
| R1-2311731 |
Clarification on SCell Type 1 virtual PHR reporting in UL CA |
Nokia, Nokia Shanghai Bell |
| R1-2311814 |
Discussion on aperiodic triggering for SRS carrier switching |
Samsung |
| R1-2311815 |
Draft CR on default beam for cross carrier scheduling |
Samsung |
| R1-2311816 |
Discussion on default beam for cross carrier scheduling |
Samsung |
| R1-2311817 |
Discussion on scheduling issue for TDD-FDD CA |
Samsung, Verizon |
| R1-2311818 |
Discussion on the remaining ambiguities with type 2 CG-PUSCH |
Samsung |
| R1-2311904 |
Scheduling restriction for FDD-TDD UL CA |
Ericsson, Verizon, Nokia, Nokia Shanghai Bell, Samsung |
| R1-2311960 |
On scheduling issue for TDD-FDD UL CA |
MediaTek Inc. |
| R1-2311961 |
Clarifying ambiguities with type 2 CG-PUSCH |
MediaTek Inc. |
| R1-2311962 |
On common PUCCH/PUSCH configuration and SUL in DCI 0_0/0_1/0_2 |
MediaTek Inc. |
| R1-2311963 |
[R16] Draft 38.212 CR on common PUCCH/PUSCH configuration and SUL in DCI 0_0/0_1/0_2 |
MediaTek Inc. |
| R1-2311964 |
[R17] Draft 38.212 CR on common PUCCH/PUSCH configuration and SUL in DCI 0_0/0_1/0_2 |
MediaTek Inc. |
| R1-2311965 |
[R18] Draft 38.212 CR on common PUCCH/PUSCH configuration and SUL in DCI 0_0/0_1/0_2 |
MediaTek Inc. |
| R1-2312010 |
Correction on fallback Type-1 HARQ-ACK codebook |
CATT |
| R1-2312015 |
Clarify several ambiguities with type 2 CG-PUSCH |
Qualcomm Incorporated |
| R1-2312016 |
Clarify CSI feedback with SUL |
Qualcomm Incorporated |
| R1-2312017 |
Clarification on presence of SUL bit in DCI |
Qualcomm Incorporated |
| R1-2312018 |
Issues on SRS carrier switching |
Qualcomm Incorporated |
| R1-2312019 |
Discussion on scheduling issue for TDD-FDD UL CA |
Qualcomm Incorporated |
| R1-2312020 |
Discussion on PUSCH selection rule for UCI multiplexing |
Qualcomm Incorporated |
| R1-2312021 |
Clarification on CSI dropping with UCI multiplexing on PUSCH |
Qualcomm Incorporated |
| R1-2312075 |
Correction on fallback Type-1 HARQ-ACK codebook |
CATT |
| R1-2312077 |
Correction on fallback Type-1 HARQ-ACK codebook |
CATT |
| R1-2312117 |
On CSI multiplexing in absence of multi-CSI-PUCCH-ResourceList |
Nokia, Nokia Shanghai Bell |
| R1-2312118 |
Clarification to multi-CSI-PUCCH-ResourceList |
Nokia, Nokia Shanghai Bell, Qualcomm Inc. |
| R1-2312170 |
Continuation on RAN1#114bis discussion on CSI feedback with SUL |
Nokia, Nokia Shanghai Bell |
| R1-2312178 |
Correction on NR Sidelink |
Philips International B.V. |
| R1-2312179 |
Correction on NR Sidelink |
Philips International B.V. |
| R1-2312181 |
Correction on NR Sidelink |
Philips International B.V. |
| R1-2312196 |
SRS Carrier Switching with DL DCI formats |
Ericsson, T-Mobile USA, Verizon |
| R1-2312200 |
On aperiodic triggering support for SRS carrier switching |
Nokia, Nokia Shanghai Bell |
| R1-2312201 |
On CG-PUSCH ambiguities |
Nokia, Nokia Shanghai Bell |
| R1-2312202 |
On PUSCH selection rule for UCI multiplexing |
Nokia, Nokia Shanghai Bell |
| R1-2312206 |
Removal of TBS limitation for HARQ retransmissions with reserved MCS |
Nokia, Nokia Shanghai Bell |
| R1-2312218 |
CR on Inter-RAT case for SL measurements |
Huawei, HiSilicon |
| R1-2312222 |
Discussion on the HARQ-ACK Multiplexing in Multi-PUSCH scheduling |
Huawei, HiSilicon |
| R1-2312224 |
Clarifications relating to type 2 CG-PUSCH |
Huawei, HiSilicon |
| R1-2312225 |
Discussion on PUSCH selection rule for UCI multiplexing |
Huawei, HiSilicon |
| R1-2312226 |
Clarification on HARQ feedback for TDD-FDD UL CA |
Huawei, HiSilicon |
| R1-2312228 |
Discussion on DL DCI triggering for SRS carrier switching |
Huawei, HiSilicon |
| R1-2312233 |
Draft CR on power control parameters for PHR of SCell |
Huawei, HiSilicon |
| R1-2312234 |
Discussion on power control parameters for PHR of SCell |
Huawei, HiSilicon |
| R1-2312235 |
Correction on the order of SRS transmissions on multiple uplinks triggered by DCI 2_3 for SRS carrier switching |
Huawei, HiSilicon |
| R1-2312236 |
Discussion on the order of SRS transmissions on multiple uplinks triggered by DCI 2_3 for SRS carrier switching |
Huawei, HiSilicon |
| R1-2312242 |
Discussion on PUSCH selection rule for UCI multiplexing |
Ericsson |
| R1-2312243 |
Discussion on first SPS PDSCH and multiplexing timeline |
Ericsson |
| R1-2312341 |
Moderator summary #1 of clarifying several ambiguities with type 2 CG-PUSCH |
Moderator (Qualcomm) |
| R1-2312352 |
Summary of discussion on PUSCH selection rule for UCI multiplexing |
Moderator (vivo) |
| R1-2312353 |
Summary on CSI reporting for 1 CSI-RS port on PUSCH |
Moderator (ZTE) |
| R1-2312363 |
Correction on the order of SRS transmissions on multiple uplinks triggered by DCI 2_3 for SRS carrier switching |
Huawei, HiSilicon, Samsung |
| R1-2312364 |
Correction on the order of SRS transmissions on multiple uplinks triggered by DCI 2_3 for SRS carrier switching |
Huawei, HiSilicon, Samsung |
| R1-2312365 |
Correction on the order of SRS transmissions on multiple uplinks triggered by DCI 2_3 for SRS carrier switching |
Huawei, HiSilicon, Samsung |
| R1-2312366 |
Summary of discussion on slot offset calculation for PUSCH carrying AP CSI without UL TB |
Moderator (Apple Inc.) |
| R1-2312372 |
Summary of discussion on default beam for cross-carrier scheduling |
Moderator (Samsung) |
| R1-2312376 |
Summary of discussion on scheduling issue for TDD-FDD UL CA |
Moderator (Samsung) |
| R1-2312430 |
Summary of discussion on SRS transmission occasion |
Moderator (vivo) |
| R1-2312435 |
FL summary on "memory for slot offset for ACSI without data |
Moderator (Apple) |
| R1-2312437 |
Summary of PHR reporting for overlapping PUSCHs |
Moderator (CATT) |
| R1-2312438 |
Summary of fallback Type-1 HARQ-ACK codebook |
Moderator (CATT) |
| R1-2312439 |
Summary of clarification on the first SPS PDSCH and Type2 CG PUSCH |
Moderator (CATT) |
| R1-2312440 |
Moderator summary #1 on clarification on CSI dropping with UCI multiplexing on PUSCH |
Moderator (Qualcomm) |
| R1-2312441 |
Summary on default pathloss reference signal for SRS and PUCCH |
Moderator (Google) |
| R1-2312446 |
Draft LS to RAN2 on introduction of simultaneous PUCCH and PUSCH transmission with same priority |
Samsung |
| R1-2312450 |
Draft CR on Simultaneous PUCCH and PUSCH transmission with same priority in UL CA |
Moderator (Samsung), Ericsson, Verizon |
| R1-2312451 |
Draft CR on Simultaneous PUCCH and PUSCH transmission with same priority in UL CA |
Moderator (Samsung), Ericsson, Verizon |
| R1-2312456 |
LS to RAN2 on introduction of simultaneous PUCCH and PUSCH transmission with same priority |
RAN1, Samsung |
| R1-2312459 |
Summary of NR Rel-15/16 maintenance discussion for aperiodic triggering support for SRS carrier switching |
Moderator (Ericsson) |
| R1-2312463 |
[115-R15/16-NR] Summary on SCell Type 1 virtual PHR report derivation |
Moderator (Nokia) |
| R1-2312464 |
[115-R15/16-NR] Summary on Clarification to multi-CSI-PUCCH-ResourceList |
Moderator (Nokia) |
| R1-2312465 |
[115-R15/R16-NR] Removal of TBS limitation for HARQ retransmissions with reserved MCS |
Moderator (Nokia) |
| R1-2312466 |
Draft CR on slot offset calculation for PUSCH carrying aperiodic CSI with no transport block |
Moderator (Apple), Nokia, Nokia Shanghai Bell, Ericsson, Samsung |
| R1-2312467 |
Draft CR on slot offset calculation for PUSCH carrying aperiodic CSI with no transport block |
Moderator (Apple), Nokia, Nokia Shanghai Bell, Ericsson, Samsung |
| R1-2312468 |
Draft CR on slot offset calculation for PUSCH carrying aperiodic CSI with no transport block |
Moderator (Apple), Nokia, Nokia Shanghai Bell, Ericsson, Samsung |
| R1-2312483 |
CR on default pathloss reference signal for SRS and PUCCH |
Moderator (Google), Google, Ericsson |
| R1-2312484 |
CR on default pathloss reference signal for SRS and PUCCH |
Moderator (Google), Google, Ericsson |
| R1-2312485 |
CR on default pathloss reference signal for SRS and PUCCH |
Moderator (Google), Google, Ericsson |
| R1-2312486 |
Draft CR on Memory issue associated to slot offset determination for A-CSI without data |
Moderator (Apple), Samsung |
| R1-2312487 |
Draft CR on Memory issue associated to slot offset determination for A-CSI without data |
Moderator (Apple), Samsung |
| R1-2312488 |
Draft CR on Memory issue associated to slot offset determination for A-CSI without data |
Moderator (Apple), Samsung |
| R1-2312493 |
Summary of discussion on the HARQ-ACK Multiplexing in Multi-PUSCH scheduling |
Moderator (Huawei) |
| R1-2312512 |
Correction on fallback Type-1 HARQ-ACK codebook |
CATT, Samsung, New H3C |
| R1-2312523 |
Correction on NR Sidelink |
Philips International B.V., Huawei, HiSilicon |
| R1-2312524 |
Correction on NR Sidelink |
Philips International B.V., Huawei, HiSilicon |
| R1-2312525 |
Correction on NR Sidelink |
Philips International B.V., Huawei, HiSilicon |
| R1-2312528 |
CR on slot offset calculation for PUSCH carrying aperiodic CSI with no transport block |
Moderator (Apple), Nokia, Nokia Shanghai Bell, Ericsson, Samsung |
| R1-2312529 |
CR on slot offset calculation for PUSCH carrying aperiodic CSI with no transport block |
Moderator (Apple), Nokia, Nokia Shanghai Bell, Ericsson, Samsung |
| R1-2312530 |
CR on slot offset calculation for PUSCH carrying aperiodic CSI with no transport block |
Moderator (Apple), Nokia, Nokia Shanghai Bell, Ericsson, Samsung |
| R1-2312552 |
Summary of Discussion on inter-RAT sidelink measurements |
Moderator (Huawei) |
| R1-2312592 |
FL summary on Clarification on SUL |
Moderator (Qualcomm) |
| R1-2312598 |
Clarification on the first SPS PDSCH and Type2 CG PUSCH |
CATT, Apple |
| R1-2312599 |
CR on Memory issue associated to slot offset determination for A-CSI without data |
Moderator (Apple), Nokia, Nokia Shanghai Bell, Samsung |
| R1-2312600 |
CR on Memory issue associated to slot offset determination for A-CSI without data |
Moderator (Apple), Nokia, Nokia Shanghai Bell, Samsung |
| R1-2312601 |
CR on Memory issue associated to slot offset determination for A-CSI without data |
Moderator (Apple), Nokia, Nokia Shanghai Bell, Samsung |
| R1-2312619 |
Summary#2 of discussion on SRS transmission occasion |
Moderator (vivo) |
| R1-2312626 |
CR on Simultaneous PUCCH and PUSCH transmission with same priority in UL CA |
Samsung, Ericsson, Verizon, Nokia, Nokia Shanghai Bell, ZTE |
| R1-2312627 |
CR on Simultaneous PUCCH and PUSCH transmission with same priority in UL CA |
Samsung, Ericsson, Verizon, Nokia, Nokia Shanghai Bell, ZTE |
| R1-2312628 |
Draft CR on Simultaneous PUCCH and PUSCH transmission with same priority in UL CA |
Samsung, Ericsson, Verizon, Nokia, Nokia Shanghai Bell |
| R1-2312634 |
Clarification on the first SPS PDSCH and Type2 CG PUSCH |
CATT, Apple, Ericsson |
| R1-2312635 |
Clarification on the first SPS PDSCH and Type2 CG PUSCH |
CATT, Apple, Ericsson |
| R1-2312640 |
Summary#2 of NR Rel-15/16 maintenance discussion for aperiodic triggering support for SRS carrier switching |
Moderator (Ericsson) |
| R1-2312665 |
Summary#2 of discussion on the HARQ-ACK Multiplexing in Multi-PUSCH scheduling |
Moderator (Huawei) |
| R1-2312673 |
Correction for SRS carrier switching for DCI formats 1_1 and 1_2 |
Ericsson, T-Mobile USA, Verizon, Samsung |
| R1-2312674 |
Correction for SRS carrier switching for DCI formats 1_1 and 1_2 |
Ericsson, T-Mobile USA, Verizon, Samsung |
| R1-2312675 |
Correction on CSI reporting for 1 CSI-RS port |
ZTE, Huawei, HiSilicon, Ericsson, Samsung |
| R1-2312676 |
Correction on CSI reporting for 1 CSI-RS port |
ZTE, Huawei, HiSilicon, Ericsson, Samsung |
| R1-2312689 |
Summary#2 of Discussion on inter-RAT sidelink measurements |
Moderator (Huawei) |
| R1-2312691 |
CR on applicability of sidelink measurements |
Huawei, HiSilicon, Qualcomm, Nokia, Nokia Shanghai Bell, Samsung |
| R1-2312692 |
CR on applicability of sidelink measurements |
Huawei, HiSilicon, Qualcomm, Nokia, Nokia Shanghai Bell, Samsung |
| R1-2312693 |
CR on applicability of sidelink measurements |
Huawei, HiSilicon, Qualcomm, Nokia, Nokia Shanghai Bell, Samsung |
| 7.2 |
Maintenance on NR Release 17 |
|
| R1-2310834 |
Draft CR on Type-1 HARQ-ACK codebook on PUCCH |
Huawei, HiSilicon, CBN |
| R1-2310835 |
Draft CR on fallback Type-1 HARQ codebook |
Huawei, HiSilicon, CBN |
| R1-2310873 |
Correction on SRS antenna switching configuration |
Huawei, HiSilicon |
| R1-2310910 |
Discussion on scaling of angles for CDL models |
Ericsson |
| R1-2310911 |
Draft CR on scaling of angles for CDL models |
Ericsson |
| R1-2310913 |
Draft CR correcting reference to a figure in 38.901 |
Ericsson |
| R1-2310945 |
Draft CR on scaling of angles for CDL models |
Ericsson |
| R1-2310946 |
Draft CR correcting reference to a figure in 38.901 |
Ericsson |
| R1-2310963 |
Draft CR on SRS for antenna switching |
ZTE |
| R1-2310983 |
Correction on SRS transmission outside initial UL BWP in RRC_INACTIVE mode |
Nokia, Nokia Shanghai Bell |
| R1-2310990 |
Rel-17 RedCap maintenance issues |
ZTE, Sanechips |
| R1-2310991 |
Corrections on MBS for Redcap |
ZTE, Sanechips |
| R1-2311013 |
Draft CR on Type-1 HARQ-ACK codebook for MBS |
ZTE, CBN |
| R1-2311014 |
Draft CR on the type 1 HARQ-ACK codebook in PUSCH |
ZTE, CBN |
| R1-2311015 |
Discussion on the HARQ-ACK multiplexing for MBS and unicast |
ZTE, CBN |
| R1-2311016 |
Draft CR on DCI fields assumption with disabled HARQ-ACK information |
ZTE, CBN |
| R1-2311017 |
Draft CR on the last multicast DCI for PUCCH resource determination |
ZTE, CBN |
| R1-2311018 |
Draft CR on RV determination for PDSCH repetitions for MBS |
ZTE, CBN |
| R1-2311077 |
Maintenance for Rel-17 RedCap |
vivo |
| R1-2311078 |
Draft CR on processing time for MBS PDSCH without HARQ-ACK feedback |
vivo |
| R1-2311079 |
Draft CR on type 1 codebook on PUSCH with fallback operation |
vivo |
| R1-2311080 |
Draft CR on type 1 codebook with MBS PDSCH repetition |
vivo |
| R1-2311081 |
Discussion on DCI indication for HARQ-ACK retransmission and SCell dormancy |
vivo |
| R1-2311082 |
Draft CR on DCI indication for HARQ-ACK retransmission and SCell dormancy |
vivo |
| R1-2311196 |
Discussion on angle scaling for CDL model |
ZTE |
| R1-2311253 |
Draft CR on transmission timing adjustments for Rel-17 NR-NTN |
OPPO |
| R1-2311292 |
Remaining issues of Rel-17 RedCap |
CATT |
| R1-2311293 |
Draft CR on determining p0 for multi-TRP PUSCH transmission |
CATT |
| R1-2311294 |
Draft CR on determining p0 for PUSCH transmission |
CATT |
| R1-2311295 |
Draft CR on determining power control adjustment state for PUSCH transmission |
CATT |
| R1-2311296 |
Draft CR on power control for multi-TRP PUSCH transmission |
CATT |
| R1-2311297 |
Draft CR on determining power control parameter for SRS transmission |
CATT |
| R1-2311298 |
Correction on PUCCH power control parameter determination |
CATT, Nokia, Nokia Shanghai Bell, Samsung |
| R1-2311299 |
Draft CR on fallback Type-1 HARQ-ACK codebook on PUSCH without UL DAI field |
CATT, CBN |
| R1-2311300 |
Draft CR on fallback Type-1 HARQ-ACK codebook on PUSCH with a UL DAI field |
CATT, CBN |
| R1-2311301 |
Discussion on fallback Type-1 CB on PUSCH with two UL DAI fields |
CATT, CBN |
| R1-2311302 |
Draft CR on fallback Type-1 CB on PUSCH with two UL DAI fields |
CATT, CBN |
| R1-2311303 |
Draft CR on Type-2 HARQ-ACK codebook determination for only one of unicast or multicast |
CATT, CBN |
| R1-2311304 |
Draft CR on not supporting enhanced Type-2 HARQ codebook for multicast |
CATT, CBN |
| R1-2311305 |
Draft CR on n_harq-ack value determination when only one of unicast or multicast with Type-1 HARQ-ACK CB |
CATT, CBN |
| R1-2311306 |
Draft CR on n_harq-ack value determination when unicast with enhanced Type-2 HARQ-ACK CB |
CATT, CBN |
| R1-2311307 |
Draft CR on multicast disabled HARQ-ACK information in Type-3 HARQ codebook |
CATT, CBN |
| R1-2311308 |
Draft CR on DCI scrambled with G-RNTI for multicast to 38.213 |
CATT, CBN |
| R1-2311309 |
Draft CR on DCI scrambled with G-RNTI for multicast to 38.214 |
CATT, CBN |
| R1-2311310 |
Discussion on issues of CSI related timeline for 480/960 kHz |
CATT |
| R1-2311311 |
Correction on HARQ feedback for TCI state update indication |
CATT |
| R1-2311374 |
Discussion on the enhanced Type-2 HARQ-ACK codebook |
CATT, CBN |
| R1-2311379 |
Discussion on remaining issues for RedCap |
xiaomi |
| R1-2311472 |
Draft CR on PDSCH processing timeline without HARQ feedback |
CMCC |
| R1-2311473 |
Draft CR on PUCCH repetition for RedCap |
CMCC |
| R1-2311537 |
Discussion on angle scaling procedure for CDL channel in TR38.901 |
Intel Corporation |
| R1-2311538 |
Draft Correction of angle scaling procedure for CDL channel in TR38.901 |
Intel Corporation |
| R1-2311580 |
Draft CR on UL beam after 2-step RACH |
Google |
| R1-2311581 |
Discussion on default beam and pathloss reference signal based on unified TCI framework |
Google |
| R1-2311582 |
Draft CR on default pathloss reference signal based on unified TCI framework |
Google |
| R1-2311583 |
Draft CR on default beam based on unified TCI framework |
Google |
| R1-2311607 |
Discussion on remaining issues for RedCap UE |
NTT DOCOMO, INC. |
| R1-2311608 |
Draft CR on paging occasions and CG-SDT for HD-FDD RedCap |
NTT DOCOMO, INC. |
| R1-2311609 |
Discussion on NDI and RV for the scheduled PXSCHs when BWP switching is indicated |
NTT DOCOMO, INC. |
| R1-2311610 |
Draft CR on NDI/RV for the scheduled PXSCHs when BWP switching is indicated |
NTT DOCOMO, INC. |
| R1-2311611 |
Discussion on NCJT CMR restriction |
NTT DOCOMO, INC. |
| R1-2311673 |
Discussion on PUCCH power control |
Apple |
| R1-2311765 |
Corrections on RRC parameter names for feMIMO in TS38.212 |
Sharp |
| R1-2311776 |
Draft CR on determination of processing time for MBS PDSCH without feedback |
NTT DOCOMO, INC. |
| R1-2311778 |
Draft CR on resource allocation in time domain for multi-PXSCH scheduling |
vivo |
| R1-2311779 |
Draft CR on Type-2 HARQ-ACK codebook for multi-PDSCH scheduling |
vivo |
| R1-2311780 |
Draft CR on spatial relation configuration for SRS |
CATT |
| R1-2311785 |
Maintenance issues for Rel-17 NR RedCap |
Nokia, Nokia Shanghai Bell |
| R1-2311789 |
Remaining Rel-17 issues for MBS |
Nokia, Nokia Shanghai Bell |
| R1-2311790 |
Draft CR on intra-UE multiplexing for multicast |
Nokia, Nokia Shanghai Bell |
| R1-2311791 |
Draft CR on Type-1 HARQ-ACK Codebook with Repetitions |
Nokia, Nokia Shanghai Bell |
| R1-2311819 |
Draft CR on unified TCI state indication via DCI format 1_2 |
Samsung |
| R1-2311822 |
Discussion on colliding SRS transmission symbol drop |
Samsung |
| R1-2311823 |
Draft CR on colliding SRS transmission symbol drop |
Samsung |
| R1-2311824 |
Discussion on angle scaling for CDL channel in TR38.901 |
Samsung |
| R1-2311825 |
Discussion on pending draft CRs on MBS from RAN1#114bis |
Samsung |
| R1-2311826 |
Correction on processing time for multicast PDSCH without HARQ-ACK report |
Samsung |
| R1-2311827 |
Correction on Type-1 HARQ-ACK fallback operation in PUSCH |
Samsung |
| R1-2311893 |
Discussion on CSI related timeline for 480/960 kHz |
LG Electronics |
| R1-2311909 |
Maintenance of PDCCH monitoring adaptation for UE power saving |
Nokia, Nokia Shanghai Bell |
| R1-2311910 |
Correction of PDCCH monitoring adaptation behaviour for DRX groups |
Nokia, Nokia Shanghai Bell |
| R1-2311954 |
Discussion on the conditions and behaviors for CG-UCI and HARQ-ACK dropping and multiplexing in 38.213 |
Sharp |
| R1-2311955 |
Adding conditions on CG-UCI and HARQ-ACK dropping procedures in 38.213 |
Sharp |
| R1-2311966 |
On frequencyDomainAllocation for R17 Idle mode TRS in R17 UE power saving |
MediaTek Inc. |
| R1-2311967 |
Draft CR for PUCCH resource determination for NACK-only mode 1 with one bit HARQ-ACK |
MediaTek Inc. |
| R1-2311968 |
Draft CR for 38.213 on UL resource counting with SSB in unpaired spectrum |
MediaTek Inc. |
| R1-2311969 |
Draft CR for 38.214 on UL resource counting with SSB in unpaired spectrum |
MediaTek Inc. |
| R1-2311970 |
RedCap remaining issues with CG-SDT |
MediaTek Inc. |
| R1-2312022 |
Draft CR on multicast repetition number for Type-1 HARQ-ACK codebook |
Qualcomm Incorporated |
| R1-2312023 |
Draft CR on collision avoidance between PDCCH in Type0/0B CSS and dedicated RRC scheduled UL for HD-FDD RedCap UEs |
Qualcomm Incorporated |
| R1-2312024 |
Draft CR on PDSCH configuration for MBS broadcast |
Qualcomm Incorporated |
| R1-2312076 |
Correction on HARQ feedback for TCI state update indication |
CATT |
| R1-2312078 |
Correction on PUCCH power control parameter determination |
CATT, Nokia, Nokia Shanghai Bell, Samsung, Apple, Huawei |
| R1-2312089 |
Draft CR on HARQ-ACK codebook generation for multicast and unicast with different codebook types |
ZTE, CBN |
| R1-2312097 |
Discussion on CSI related timeline for 480/960 kHz |
Ericsson |
| R1-2312098 |
Discussion on NDI/RV for scheduled PxSCHs when BWP switching is indicated |
Ericsson |
| R1-2312099 |
Correction related to periodicity of TRS occasions |
Ericsson |
| R1-2312143 |
Draft CR on UE receiving both unicast and MBS broadcast |
Huawei, HiSilicon, CMCC, CBN |
| R1-2312144 |
Draft CR on PDSCH processing timeline |
Huawei, HiSilicon, CBN |
| R1-2312160 |
Discussion on Issues with Scaling of Angles with TR 38.901 CDL Channel Model |
Nokia, Nokia Shanghai Bell |
| R1-2312166 |
On the PBCH payload of NCD-SSB |
Ericsson |
| R1-2312212 |
Discussion on the maintenance issues for Rel-17 MBS |
Huawei, HiSilicon, CBN |
| R1-2312214 |
Discussion on SRS spatial relation |
Huawei, HiSilicon |
| R1-2312215 |
Correction to SRS spatial relation |
Huawei, HiSilicon |
| R1-2312220 |
Discussion on the CSI related timeline for 480 and 960 kHz SCS in FR2-2 |
Huawei, HiSilicon |
| R1-2312221 |
Discussion on the NDI and RV fields in PDCCH scheduling multiple PxSCH during BWP switching |
Huawei, HiSilicon |
| R1-2312232 |
Discussion on skipping UL transmission for Rel-17 TBoMS |
Huawei, HiSilicon |
| R1-2312240 |
Discussion on NCJT CMR restriction |
Huawei, HiSilicon |
| R1-2312241 |
Discussion on scaling of angles for CDL channel model in TR38.901 |
Huawei, HiSilicon |
| R1-2312276 |
FL summary #1 on Rel-17 RedCap maintenance |
Moderator (Ericsson) |
| R1-2312277 |
FL summary #2 on Rel-17 RedCap maintenance |
Moderator (Ericsson) |
| R1-2312278 |
FL summary #3 on Rel-17 RedCap maintenance |
Moderator (Ericsson) |
| R1-2312279 |
RAN1 agreements for Rel-17 NR RedCap |
Rapporteur (Ericsson) |
| R1-2312285 |
FLS#1 on the maintenance issues for Rel-17 NR MBS |
Moderator (Huawei) |
| R1-2312286 |
FLS#2 on the maintenance issues for Rel-17 NR MBS |
Moderator (Huawei) |
| R1-2312287 |
FLS#3 on the maintenance issues for Rel-17 NR MBS |
Moderator (Huawei) |
| R1-2312288 |
FLS#4 on the maintenance issues for Rel-17 NR MBS |
Moderator (Huawei) |
| R1-2312289 |
Draft CR on Type-1 HARQ-ACK codebook on PUSCH |
Moderator (Huawei), [Samsung, CATT, vivo, ZTE] |
| R1-2312290 |
Draft CR on Type-1 HARQ-ACK codebook on PUCCH |
Moderator (Huawei), Samsung |
| R1-2312291 |
Draft CR on multiplexing enhanced Type-2 and Type-2 HARQ-ACK codebook |
Moderator (Huawei), [CATT] |
| R1-2312292 |
Draft CR on PDSCH processing timeline |
Moderator (Huawei) |
| R1-2312310 |
Summary #1 of discussion on scaling of angles for CDL models |
Moderator (Ericsson) |
| R1-2312311 |
Summary #2 of discussion on scaling of angles for CDL models |
Moderator (Ericsson) |
| R1-2312323 |
Correction on PUCCH power control parameter determination |
CATT, Nokia, Nokia Shanghai Bell, Samsung, Apple, Huawei, Ericsson, vivo |
| R1-2312330 |
Moderator summary#1 of Rel-17 URLLC & IIoT maintenance |
Moderator (Nokia) |
| R1-2312350 |
Moderator Summary#1 of Maintenance on Rel-17 SRS |
Moderator (ZTE) |
| R1-2312351 |
Summary #1 of FR2-2 maintenance |
Moderator (LG Electronics) |
| R1-2312354 |
Moderator Summary #1 for Maintenance on Rel-17 Multi-Beam |
Moderator (ZTE) |
| R1-2312356 |
Summary for maintenance on UE power saving enhancements |
Moderators (Ericsson, MediaTek, Nokia) |
| R1-2312357 |
Summary for Rel.17 NR FeMIMO maintenance: mTRP UL |
Moderator (Nokia) |
| R1-2312378 |
Correction on PUCCH power control parameter determination |
CATT, Nokia, Nokia Shanghai Bell, Samsung, Apple, Huawei, Ericsson, vivo |
| R1-2312379 |
Correction on PUCCH power control parameter determination |
CATT, Nokia, Nokia Shanghai Bell, Samsung, Apple, Huawei, Ericsson, vivo |
| R1-2312421 |
FLS#1 on positioning SRS spatial relation |
Moderator (Huawei) |
| R1-2312422 |
FLS#2 on positioning SRS spatial relation |
Moderator (Huawei) |
| R1-2312428 |
Moderator summary#2 of Rel-17 URLLC & IIoT maintenance |
Moderator (Nokia) |
| R1-2312436 |
Moderator Summary for Rel.17 NR FeMIMO maintenance CSI enhancement |
Moderator (Huawei) |
| R1-2312452 |
Moderator Summary #2 for Maintenance on Rel-17 Multi-Beam |
Moderator (ZTE) |
| R1-2312453 |
Correction on HARQ feedback for TCI state update indication |
Moderator (ZTE), CATT, Samsung |
| R1-2312454 |
Correction on HARQ feedback for TCI state update indication |
Moderator (ZTE), CATT, Samsung |
| R1-2312455 |
FLS#1 on colliding SRS transmission symbol drop |
Moderator (Samsung) |
| R1-2312461 |
CR on transmission timing adjustments for Rel-17 NR-NTN |
OPPO, THALES, ZTE |
| R1-2312462 |
CR on transmission timing adjustments for Rel-17 NR-NTN |
OPPO, THALES, ZTE |
| R1-2312470 |
Correction on Type-2 HARQ-ACK codebook for multi-slot scheduling |
Moderator (LG Electronics), Samsung, Ericsson, vivo, NTT DOCOMO, INC., ZTE, Sanechips, Huawei, HiSilicon |
| R1-2312471 |
Correction on Type-2 HARQ-ACK codebook for multi-slot scheduling |
Moderator (LG Electronics), Samsung, Ericsson, vivo, NTT DOCOMO, INC., ZTE, Sanechips, Huawei, HiSilicon |
| R1-2312474 |
Summary #2 of FR2-2 maintenance |
Moderator (LG Electronics) |
| R1-2312475 |
Correction on CSI related timeline for 480/960 kHz |
Moderator (LG Electronics), NTT DOCOMO, INC., Samsung, ZTE, Sanechips, Huawei, HiSilicon, Ericsson |
| R1-2312476 |
Correction on CSI related timeline for 480/960 kHz |
Moderator (LG Electronics), NTT DOCOMO, INC., Samsung, ZTE, Sanechips, Huawei, HiSilicon, Ericsson |
| R1-2312477 |
Correction on CSI related timeline for 480/960 kHz |
Moderator (LG Electronics), NTT DOCOMO, INC., Samsung, ZTE, Sanechips, Huawei, HiSilicon, Ericsson |
| R1-2312478 |
Correction on CSI related timeline for 480/960 kHz |
Moderator (LG Electronics), NTT DOCOMO, INC., Samsung, ZTE, Sanechips, Huawei, HiSilicon, Ericsson |
| R1-2312479 |
CR on resource allocation in time domain for multi-PXSCH scheduling |
Moderator (LG Electronics), vivo, Ericsson, NTT DOCOMO, INC., Samsung, ZTE, Sanechips, Huawei, HiSilicon |
| R1-2312480 |
CR on resource allocation in time domain for multi-PXSCH scheduling |
Moderator (LG Electronics), vivo, Ericsson, NTT DOCOMO, INC., Samsung, ZTE, Sanechips, Huawei, HiSilicon |
| R1-2312481 |
CR on resource allocation in time domain for multi-PXSCH scheduling |
Moderator (LG Electronics), vivo, Ericsson, NTT DOCOMO, INC., Samsung, ZTE, Sanechips, Huawei, HiSilicon |
| R1-2312482 |
CR on resource allocation in time domain for multi-PXSCH scheduling |
Moderator (LG Electronics), vivo, Ericsson, NTT DOCOMO, INC., Samsung, ZTE, Sanechips, Huawei, HiSilicon |
| R1-2312489 |
Summary#2 for maintenance on UE power saving enhancements |
Moderators (Ericsson, MediaTek, Nokia) |
| R1-2312492 |
Correction of PDCCH monitoring adaptation behaviour for DRX groups |
Nokia, Nokia Shanghai Bell, MediaTek |
| R1-2312498 |
Session notes for 7.2 (Maintenance on supporting NR from 52.6GHz to 71 GHz) |
Ad-Hoc Chair (Huawei) |
| R1-2312499 |
Session notes for 7.2 (Maintenance on NR Multicast and Broadcast Services) |
Ad-Hoc Chair (Huawei) |
| R1-2312500 |
Session notes for 7.2 (Maintenance on Solutions for NR to support non-terrestrial networks) |
Ad-Hoc Chair (Huawei) |
| R1-2312501 |
Session notes for 7.2 (Maintenance on Support of reduced capability NR devices) |
Ad-Hoc Chair (Huawei) |
| R1-2312502 |
Session notes for 7.2 (Maintenance on NR positioning enhancements) |
Ad-Hoc Chair (Huawei) |
| R1-2312519 |
Draft LS on PBCH payload of NCD-SSB |
Ericsson |
| R1-2312520 |
LS on PBCH payload of NCD-SSB |
RAN1, Ericsson |
| R1-2312521 |
Draft Reply LS on monitoring of paging occasions for CG-SDT with HD-FDD RedCap UEs |
Ericsson |
| R1-2312522 |
Reply LS on monitoring of paging occasions for CG-SDT with HD-FDD RedCap UEs |
RAN1, Ericsson |
| R1-2312527 |
FLS#2 on colliding SRS transmission symbol drop |
Moderator (Samsung) |
| R1-2312533 |
Summary of discussions on skipping UL transmission and R17 TBoMS |
Moderator (Huawei) |
| R1-2312544 |
Correction of PDCCH monitoring adaptation behaviour for DRX groups |
Nokia, Nokia Shanghai Bell, MediaTek, Ericsson |
| R1-2312545 |
Correction of PDCCH monitoring adaptation behaviour for DRX groups |
Nokia, Nokia Shanghai Bell, MediaTek, Ericsson |
| R1-2312548 |
CR on UL beam after 2-step RACH |
Moderator (ZTE), Google, Samsung, ZTE |
| R1-2312549 |
CR on UL beam after 2-step RACH |
Moderator (ZTE), Google, Samsung, ZTE |
| R1-2312550 |
CR on default beam based on unified TCI framework |
Moderator (ZTE), Google, Samsung, ZTE |
| R1-2312551 |
CR on default beam based on unified TCI framework |
Moderator (ZTE), Google, Samsung, ZTE |
| R1-2312554 |
FLS#3 on positioning SRS spatial relation |
Moderator (Huawei) |
| R1-2312555 |
CR on Type-1 HARQ-ACK codebook on PUSCH |
Moderator (Huawei), Samsung, CATT, vivo, ZTE |
| R1-2312556 |
CR on Type-1 HARQ-ACK codebook on PUSCH |
Moderator (Huawei), Samsung, CATT, vivo, ZTE |
| R1-2312557 |
CR on PDCCH monitoring in Type0B CSS for HD-FDD RedCap UEs |
Moderator (Huawei), Qualcomm |
| R1-2312558 |
CR on PDCCH monitoring in Type0B CSS for HD-FDD RedCap UEs |
Moderator (Huawei), Qualcomm |
| R1-2312559 |
CR correcting scaling of angles for CDL model and a figure reference |
Ericsson, Samsung, Intel, Nokia, Nokia Shanghai Bell, ZTE |
| R1-2312562 |
Draft CR on HARQ-ACK for SPS PDSCH |
Moderator (Huawei) |
| R1-2312591 |
Draft LS on periodicity of TRS resources for idle/inactive UEs |
Ericsson |
| R1-2312593 |
Correction to the SRS transmission collision |
Moderator (Samsung) |
| R1-2312594 |
Correction to the SRS transmission collision |
Moderator (Samsung) |
| R1-2312595 |
Correction to the SRS transmission collision |
Moderator (Samsung) |
| R1-2312596 |
Moderator summary#3 of Rel-17 URLLC & IIoT maintenance |
Moderator (Nokia) |
| R1-2312597 |
[Draft] LS on Rel-17 URLLC/IIoT required RRC parameter description change in 38.331 |
Moderator (Nokia) |
| R1-2312605 |
Summary#2 of discussions on skipping UL transmission and R17 TBoMS |
Moderator (Huawei) |
| R1-2312620 |
LS on periodicity of TRS resources for idle/inactive UEs |
RAN1, Ericsson |
| R1-2312621 |
LS on Rel-17 URLLC/IIoT required RRC parameter description change in 38.331 |
RAN1, Nokia |
| R1-2312631 |
CR on clarification of CSI-RS transmission occasion for NCJT CSI |
Moderator (Huawei), NTT DOCOMO, Nokia, Samsung |
| R1-2312632 |
CR on clarification of CSI-RS transmission occasion for NCJT CSI |
Moderator (Huawei), NTT DOCOMO, Nokia, Samsung |
| R1-2312636 |
CR on HARQ-ACK for SPS PDSCH |
Moderator (Huawei), CATT, ZTE, Samsung, Qualcomm |
| R1-2312637 |
CR on HARQ-ACK for SPS PDSCH |
Moderator (Huawei), CATT, ZTE, Samsung, Qualcomm |
| R1-2312644 |
Correction of monitoring of paging occasions for CG-SDT with HD-FDD RedCap UEs |
Moderator (Ericsson) |
| R1-2312645 |
Correction of PUCCH repetition for RedCap UE with NCD-SSB in TDD |
Moderator (Ericsson) |
| R1-2312646 |
Correction of PUSCH repetition for RedCap UE with NCD-SSB in TDD |
Moderator (Ericsson) |
| R1-2312647 |
Correction of monitoring of paging occasions for CG-SDT with HD-FDD RedCap UEs |
Moderator (Ericsson) |
| R1-2312648 |
Correction of PUCCH repetition for RedCap UE with NCD-SSB in TDD |
Moderator (Ericsson) |
| R1-2312649 |
Correction of PUSCH repetition for RedCap UE with NCD-SSB in TDD |
Moderator (Ericsson) |
| R1-2312650 |
[Draft] LS on skipping UL transmission and R17 TBoMS |
Huawei |
| R1-2312651 |
LS on skipping UL transmission and R17 TBoMS |
RAN1, Huawei |
| R1-2312682 |
Correction of monitoring of paging occasions for CG-SDT with HD-FDD RedCap UEs |
Moderator (Ericsson), NTT DOCOMO, ZTE, Ericsson |
| R1-2312683 |
Correction of monitoring of paging occasions for CG-SDT with HD-FDD RedCap UEs |
Moderator (Ericsson), NTT DOCOMO, ZTE, Ericsson |
| R1-2312684 |
Correction of PUCCH repetition for RedCap UE with NCD-SSB in TDD |
Moderator (Ericsson), NTT DOCOMO, ZTE, Ericsson |
| R1-2312685 |
Correction of PUCCH repetition for RedCap UE with NCD-SSB in TDD |
Moderator (Ericsson), NTT DOCOMO, ZTE, Ericsson |
| R1-2312686 |
Correction of PUSCH repetition for RedCap UE with NCD-SSB in TDD |
Moderator (Ericsson), NTT DOCOMO, ZTE, Ericsson |
| R1-2312687 |
Correction of PUSCH repetition for RedCap UE with NCD-SSB in TDD |
Moderator (Ericsson), NTT DOCOMO, ZTE, Ericsson |
| R1-2312688 |
FL summary #4 on Rel-17 RedCap maintenance |
Moderator (Ericsson) |
| R1-2312699 |
Correction of PUCCH repetition for RedCap UE with NCD-SSB in TDD |
Moderator (Ericsson), Xiaomi, MediaTek, Ericsson |
| R1-2312700 |
Correction of PUCCH repetition for RedCap UE with NCD-SSB in TDD |
Moderator (Ericsson), Xiaomi, MediaTek, Ericsson |
| R1-2312701 |
Correction of PUSCH repetition for RedCap UE with NCD-SSB in TDD |
Moderator (Ericsson), Xiaomi, MediaTek, Ericsson |
| R1-2312702 |
Correction of PUSCH repetition for RedCap UE with NCD-SSB in TDD |
Moderator (Ericsson), Xiaomi, MediaTek, Ericsson |
| R1-2312717 |
Rel-17 editorial corrections for TS 38.212 |
Huawei |
| R1-2312718 |
Rel-17 editorial corrections for TS 38.213 |
Samsung |
| R1-2312719 |
Rel-17 editorial corrections for TS 38.214 |
Nokia |
| R1-2312720 |
Rel-17 editorial corrections for TS 38.212 (mirrored to Rel-18) |
Huawei |
| R1-2312721 |
Rel-17 editorial corrections for TS 38.213 (mirrored to Rel-18) |
Samsung |
| R1-2312722 |
Rel-17 editorial corrections for TS 38.214 (mirrored to Rel-18) |
Nokia |
| 8 |
Rel-18 |
|
| R1-2312536 |
Consolidated Rel-18 higher layers parameter list |
Moderator (Ericsson) |
| R1-2312537 |
DRAFT LS on Rel-18 higher-layers parameter list |
Moderator (Ericsson) |
| R1-2312538 |
LS on Rel-18 higher-layers parameter list |
RAN1, Ericsson |
| R1-2312539 |
Collection of updated Rel-18 higher layers parameter list |
Moderator (Ericsson) |
| R1-2312540 |
Email discussion summary on LS for Rel-18 higher layer parameters |
Moderator (Ericsson) |
| R1-2312543 |
Consolidated Rel-18 higher layers parameter list |
Moderator (Ericsson) |
| R1-2312659 |
Consolidated Rel-18 higher layers parameter list |
Moderator (Ericsson) |
| R1-2312660 |
DRAFT LS on Rel-18 higher-layers parameter list |
Moderator (Ericsson) |
| R1-2312661 |
LS on Rel-18 higher-layers parameter list |
RAN1, Ericsson |
| R1-2312662 |
Collection of updated Rel-18 higher layers parameter list |
Moderator (Ericsson) |
| R1-2312697 |
Consolidated Rel-18 higher layers parameter list |
Moderator (Ericsson) |
| R1-2312698 |
Collection of updated Rel-18 higher layers parameter list |
Moderator (Ericsson) |
| R1-2312708 |
Corrected consolidated Rel-18 higher layers parameter list |
Moderator (Ericsson) |
| R1-2312709 |
DRAFT LS on updates of the Rel-18 higher-layers parameter list |
Moderator (Ericsson) |
| R1-2312710 |
LS on updates of the Rel-18 higher-layers parameter list |
RAN1, Ericsson |
| R1-2312711 |
Introduction of RS for pathloss determination of Type 1 CG PUSCH [PL RS Type 1 CG] |
Samsung |
| R1-2312712 |
Introduction of multiplexing in a PUSCH with repetitions HARQ-ACK associated with DL assignments received after an UL grant for the PUSCH [HARQ-ACK MUX on PUSCH] |
Samsung |
| R1-2312713 |
Introduction of additional PRS configurations [1symbol_PRS] |
Ericsson |
| R1-2312714 |
Introduction of QCL-TypeD priorities for overlapping CORESETs in M-DCI/M-TRP operation [QCL-TypeD CORESET priority for M-TRP] |
Samsung |
| R1-2312715 |
Collection of updated Rel-18 higher layers parameter list |
Moderator (Ericsson) |
| R1-2312716 |
Email discussion summary on LS for Rel-18 higher layer parameters |
Moderator (Ericsson) |
| R1-2312723 |
Maintenance of further NR coverage enhancements |
Samsung |
| R1-2312724 |
Maintenance of further mobility enhancements |
Samsung |
| R1-2312725 |
Maintenance of dynamic spectrum sharing (DSS) enhancements |
Samsung |
| R1-2312726 |
Maintenance of multi-carrier enhancements for NR |
Samsung |
| R1-2312727 |
Maintenance of MIMO Evolution for Downlink and Uplink |
Samsung |
| R1-2312728 |
Maintenance of Network Controlled Repeaters |
Samsung |
| R1-2312729 |
Maintenance of network energy savings for NR |
Samsung |
| R1-2312730 |
Maintenance of expanded and improved NR positioning |
Samsung |
| R1-2312731 |
Maintenance of support for enhanced reduced capability NR devices |
Samsung |
| R1-2312732 |
Maintenance of NR sidelink evolution |
Samsung |
| R1-2312733 |
Maintenance of XR enhancements for NR |
Samsung |
| R1-2312734 |
Correction of Rel-18 MIMO evolution |
Intel Corporation |
| R1-2312735 |
Correction of Rel-18 NR NTN enhancements |
Intel Corporation |
| R1-2312736 |
Correction of Rel-18 Positioning Enhancements |
Intel Corporation |
| R1-2312737 |
Corrections on NR positioning enhancement in 38.212 |
Huawei |
| R1-2312738 |
Corrections on Rel-18 NR sidelink evolution in 38.212 |
Huawei |
| R1-2312739 |
Corrections on Rel-18 further NR Coverage enhancement in 38.212 |
Huawei |
| R1-2312740 |
Corrections on Rel-18 Further NR mobility enhancements in 38.212 |
Huawei |
| R1-2312741 |
Corrections on Rel-18 MIMO Evolution for Downlink and Uplink in 38.212 |
Huawei |
| R1-2312742 |
Corrections on Rel-18 Multi-carrier enhancements in 38.212 |
Huawei |
| R1-2312743 |
Corrections on Rel-18 network energy saving for NR in 38.212 |
Huawei |
| R1-2312744 |
Corrections on Rel-18 NR NTN enhancements in 38.212 |
Huawei |
| R1-2312745 |
Corrections on Rel-18 XR enhancements for NR in 38.212 |
Huawei |
| R1-2312746 |
Maintenance of NR Sidelink operation on shared spectrum |
Ericsson |
| R1-2312747 |
Corrections to NR Dynamic Spectrum Sharing (DSS) |
Ericsson |
| R1-2312748 |
Corrections to NR support for dedicated spectrum less than 5MHz for FR1 |
Ericsson |
| R1-2312749 |
Corrections to MIMO enhancements |
Ericsson |
| R1-2312750 |
Corrections to NR Network-controlled Repeaters |
Ericsson |
| R1-2312751 |
Corrections to positioning enhancements |
Ericsson |
| R1-2312752 |
Correction of specification support for network energy saving |
Nokia |
| R1-2312753 |
Correction of specification support for MIMO enhancements on CSI |
Nokia |
| R1-2312754 |
Correction of specification support for MIMO enhancements on uTCI_STxMP_DMRS_SRS_8Tx_2TA |
Nokia |
| R1-2312755 |
Corrections of specification support for mobility enhancements |
Nokia |
| R1-2312756 |
Correction of specification support for NR NTN enhancements |
Nokia |
| R1-2312757 |
Corrections on the support for Expanded and Improved NR Positioning |
Nokia |
| R1-2312758 |
Correction of enhancements for NR sidelink evolution |
Nokia |
| R1-2312759 |
Correction of enhanced reduced capability NR devices |
Nokia |
| R1-2312760 |
Corrections of XR Enhancements for NR |
Nokia |
| R1-2312761 |
Introduction of UL Tx switching across up to 4 bands |
Nokia |
| R1-2312762 |
Corrections to IoT (Internet of Things) NTN (non-terrestrial network) enhancements |
Motorola Mobility |
| R1-2312763 |
Corrections on further NR coverage enhancements |
Nokia |
| R1-2312766 |
Introduction of multicast reception in RRC_INACTIVE |
Ericsson |
| R1-2312767 |
Corrections to sidelink enhancements |
Ericsson |
| R1-2312768 |
Summary of email discussion [Post-115-38.212-NR_demod_enh3-Perf] |
Moderator (Huawei) |
| R1-2312769 |
Summary of email discussion [Post-115-38.212-NR_MBS_enh-Core] |
Moderator (Huawei) |
| R1-2312770 |
Summary of email discussion [Post-115-38.212-NR_MIMO_evo_DL_UL-Core] |
Moderator (Huawei) |
| R1-2312771 |
Summary of email discussion [Post-115-38.212-NR_MC_enh] |
Moderator (Huawei) |
| R1-2312772 |
Summary of email discussion [Post-115-38.212-NR_pos_enh2-Core] |
Moderator (Huawei) |
| R1-2312773 |
Summary of email discussion [Post-115-38.212-NR_SL_enh2-Core] |
Moderator (Huawei) |
| R1-2312774 |
Summary of email discussion [Post-115-38.212-Netw_Energy_NR-Core] |
Moderator (Huawei) |
| R1-2312775 |
Introduction of Rel-18 NR demodulation performance evolution |
Huawei |
| R1-2312776 |
Introduction of Rel-18 enhancements of NR Multicast and Broadcast Services |
Huawei |
| R1-2312777 |
Corrections on Rel-18 network controlled repeaters in 38.212 |
Huawei |
| R1-2312778 |
TR 38.858 v1.1.0 for study on evolution of NR duplex operation |
CMCC |
| R1-2312779 |
Editor’s summary on draft CR 38.211 for NR_pos_enh2-Core |
Moderator (Ericsson) |
| R1-2312780 |
Editor’s summary on draft CR 38.211 for NR_SL_enh2-Core |
Moderator (Ericsson) |
| R1-2312781 |
Editor’s summary on draft CR 38.211 for NR_MIMO_evo_DL_UL-Core |
Moderator (Ericsson) |
| R1-2312782 |
Maintenance of support for dedicated spectrum less than 5MHz for FR1 |
Samsung |
| R1-2312783 |
Introduction of Rel-18 enhancements of NR Multicast and Broadcast Services |
Samsung |
| R1-2312784 |
Maintenance of support for NR NTN enhancements |
Samsung |
| R1-2312785 |
Maintenance of BWP operation without restriction |
Samsung |
| R1-2312786 |
Summary of email discussions [Post-115-38.213-NR_cov_enh2] |
Moderator (Samsung) |
| R1-2312787 |
Summary of email discussions [Post-115-38.213-NR_MC_Enh] |
Moderator (Samsung) |
| R1-2312788 |
Summary of email discussions [Post-115-38.213-NR_MIMO_evo_DL_UL] |
Moderator (Samsung) |
| R1-2312789 |
Summary of email discussions [Post-115-38.213-NR_mob_enh2] |
Moderator (Samsung) |
| R1-2312790 |
Summary of email discussions [Post-115-38.213-NR_NCR] |
Moderator (Samsung) |
| R1-2312791 |
Summary of email discussions [Post-115-38.213-NR_Netw_Energy_NR] |
Moderator (Samsung) |
| R1-2312792 |
Summary of email discussions [Post-115-38.213-NR_SL_enh2] |
Moderator (Samsung) |
| R1-2312793 |
Summary of email discussions [Post-115-38.213-NR_TEI_HARQ-ACK_PUSCH] |
Moderator (Samsung) |
| R1-2312794 |
Introduction of sidelink CA and dynamic resource pool sharing for NR V2X |
Huawei (Editor) |
| R1-2312795 |
Summary of email discussion [Post-115-37.985-NR_SL_enh2-Core] |
Moderator (Huawei) |
| R1-2312796 |
Editor’s summary on draft CR 37.213 for SL-U |
Moderator (Ericsson) |
| R1-2312797 |
Release 18 TS38.202 Editor CR for multicast in RRC_INACTIVE state |
Qualcomm |
| R1-2312798 |
Release 18 TS38.202 Editor CR for SL-PRS transmission and Reception |
Qualcomm |
| R1-2312799 |
Summary of email discussions [Post-115-38.202-NR_pos_enh2] |
Moderator (Qualcomm) |
| R1-2312800 |
Summary of email discussion on the introduction of UL Tx switching across up to 4 bands in [Post-115-38.214-MC_Enh-ULSwi] |
Moderator (Nokia) |
| R1-2312801 |
Summary of email discussion on DCI in [Post-115-38.214-MC_Enh-Scheduling] |
Moderator (Nokia) |
| R1-2312802 |
Corrections on multi-cell PDSCH / PUSCH scheduling |
Nokia |
| R1-2312803 |
Summary on email discussion on Netw_Energy_NR |
Moderator (Nokia) |
| R1-2312804 |
Introduction of NR support for dedicated spectrum less than 5MHz for FR1 |
Nokia |
| R1-2312805 |
Introduction of Rel-18 enhancements of NR Multicast and Broadcast Services |
Nokia |
| R1-2312806 |
Summary on email discussion on NR_MBS_enh-Core |
Moderator (Nokia) |
| R1-2312807 |
Summary of email discussion on NR_MIMO enhancements on CSI |
Moderator (Nokia) |
| R1-2312808 |
Summary of email discussion on NR_MIMO enhancements on uTCI_STxMP_DMRS_SRS_8Tx_2TA |
Moderator (Nokia) |
| R1-2312809 |
Summary on email discussion on NR_Mob_enh2 |
Moderator (Nokia) |
| R1-2312810 |
Introduction of Network Controlled Repeaters |
Nokia |
| R1-2312811 |
Summary on email discussion on NR_NCR-Core |
Moderator (Nokia) |
| R1-2312812 |
Summary on email discussion on NR_NTN_enh-Core |
Moderator (Nokia) |
| R1-2312813 |
Summary on email discussion on NR Enhanced Positioning |
Moderator (Nokia) |
| R1-2312814 |
Summary on email discussion on Sidelink enhancements |
Moderator (Nokia) |
| R1-2312815 |
Summary on email discussion on NR_XR_enh-Core |
Moderator (Nokia) |
| R1-2312816 |
Discussion summary for TS38.215 draft CR for Rel-18 MIMO enhancements |
Moderator (Intel Corporation) |
| R1-2312817 |
Discussion summary for TS38.215 draft CR for Rel-18 positioning enhancements |
Moderator (Intel Corporation) |
| R1-2312818 |
Summary of email discussions [Post-115-36.213-IoT_NTN_enh-Core] |
Moderator (Motorola Mobility) |
| R1-2312819 |
TR 38.869 v2.0.0 for study on low-power wake up signal and receiver for NR |
vivo |
| 8.1 |
Maintenance on NR MIMO Evolution for Downlink and Uplink |
|
| R1-2311828 |
RRC parameters for Rel-18 NR MIMO |
Moderator (Samsung) |
| R1-2312358 |
Summary on reply LS on Stage-2 CR for MIMO evolution |
Moderator (NTT DOCOMO) |
| R1-2312359 |
Draft reply LS on Stage-2 CR for MIMO evolution |
Moderator (NTT DOCOMO) |
| R1-2312369 |
FL summary of discussion on draft reply LS on MIMOevo |
Moderator (Samsung) |
| R1-2312370 |
Draft reply LS on MIMOevo |
Moderator (Samsung) |
| R1-2312371 |
Reply LS on MIMOevo |
RAN1, Samsung |
| R1-2312526 |
Reply LS on Stage-2 CR for MIMO evolution |
RAN1, NTT DOCOMO |
| 8.1.1.1 |
Unified TCI framework extension for multi-TRP |
|
| R1-2310827 |
Unified TCI framework extension for multi-TRP |
FUTUREWEI |
| R1-2310866 |
Maintenance of unified TCI framework extension for multi-TRP |
Huawei, HiSilicon |
| R1-2310919 |
Maintenance on Rel-18 Unified TCI for MTRP |
InterDigital, Inc. |
| R1-2310931 |
Discussions on the remaining issue on Unified TCI framework extension for multi-TRP |
New H3C Technologies Co., Ltd. |
| R1-2310947 |
Maintenance on unified TCI framework extension for multi-TRP |
ZTE |
| R1-2310970 |
Maintenance of unified TCI framework extension for multi-TRP |
Ericsson |
| R1-2311040 |
Discussion on unified TCI framework extension for multi-TRP |
Fujitsu |
| R1-2311083 |
Maintenance on unified TCI framework extension for multi-TRP |
vivo |
| R1-2311148 |
Remaining Issues on Unified TCI Framework Extension for multi-TRP |
Intel Corporation |
| R1-2311155 |
Remaining issues on unified TCI framework extension for multi-TRP |
Spreadtrum Communications |
| R1-2311213 |
Remaining issues of unified TCI framework extension for multi-TRP |
OPPO |
| R1-2311314 |
Discussion of remaining issues on unified TCI framework extension for multi-TRP |
CATT |
| R1-2311361 |
Maintenance on unified TCI framework for multi-TRP |
Lenovo |
| R1-2311380 |
Remaining issues on unified TCI framework extension for multi-TRP |
xiaomi |
| R1-2311420 |
Remaining issues on unified TCI framework extension for multi-TRP |
NEC |
| R1-2311432 |
Unified TCI framework extension for multi-TRP/panel |
LG Electronics |
| R1-2311440 |
Maintenance on unified TCI framework extension for multi-TRP |
Google |
| R1-2311474 |
Remaining issues on unified TCI framework extension for multi-TRP |
CMCC |
| R1-2311522 |
Remaining issues on unified TCI framework extension for multi-TRP |
Panasonic |
| R1-2311591 |
Remaining issues on unified TCI framework extension for multi-TRP |
FGI |
| R1-2311612 |
Remaining issues on unified TCI framework extension for multi-TRP |
NTT DOCOMO, INC. |
| R1-2311674 |
Unified TCI framework extension for multi-TRP |
Apple |
| R1-2311718 |
Maintenance on unified TCI framework extension for multi-TRP |
Sharp |
| R1-2311739 |
Maintenance of unified TCI framework extension for multi-TRP |
Nokia, Nokia Shanghai Bell |
| R1-2311792 |
Remaining issues of unified TCI framework extension for multi-TRP |
Transsion Holdings |
| R1-2311829 |
Remaining details on unified TCI extension focusing on m-TRP |
Samsung |
| R1-2311925 |
Remaining issues on unified TCI framework extension for multi-TRP |
Ruijie Network Co. Ltd |
| R1-2311971 |
Remaining issues on unified TCI framework extension for multi-TRP |
MediaTek Inc. |
| R1-2312005 |
Remaining issues on unified TCI framework extension for multi-TRP |
Hyundai Motor Company |
| R1-2312007 |
Moderator summary on extension of unified TCI framework (Round 0) |
Moderator (MediaTek Inc.) |
| R1-2312008 |
Moderator summary on extension of unified TCI framework (Round 1) |
Moderator (MediaTek Inc.) |
| R1-2312009 |
Moderator summary on extension of unified TCI framework (Round 2) |
Moderator (MediaTek Inc.) |
| R1-2312025 |
Extension of unified TCI framework for mTRP |
Qualcomm Incorporated |
| R1-2312177 |
Multi-TRP enhancements for the unified TCI framework |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2312294 |
Remaining details on unified TCI extension focusing on m-TRP |
Samsung |
| R1-2312654 |
Moderator summary on extension of unified TCI framework (Final) |
Moderator (MediaTek Inc.) |
| 8.1.1.2 |
Two TAs for multi-DCI |
|
| R1-2310828 |
Enhancements to support two TAs for multi-DCI |
FUTUREWEI |
| R1-2310867 |
Maintenance of TA enhancement for UL M-TRP transmission |
Huawei, HiSilicon |
| R1-2310920 |
Maintenance on Rel-18 Multiple TA Operation |
InterDigital, Inc. |
| R1-2310948 |
Maintenance on TA enhancement for multi-DCI |
ZTE |
| R1-2310971 |
Maintenance of two TAs for multi-DCI |
Ericsson |
| R1-2311084 |
Maintenance on two TAs for multi-DCI-based multi-TRP operation |
vivo |
| R1-2311152 |
On two TAs for multi-DCI |
Intel Corporation |
| R1-2311156 |
Remaining issues on two TAs for multi-DCI based multi-TRP |
Spreadtrum Communications |
| R1-2311214 |
Remaining issues of two TAs for multi-DCI based multi-TRP operation |
OPPO |
| R1-2311315 |
Remaining issues on TA enhancement for multi-DCI |
CATT |
| R1-2311362 |
Remaining issues of two TAs for multi-DCI UL transmission |
Lenovo |
| R1-2311381 |
Discussion on two TAs for multi-TRP operation |
xiaomi |
| R1-2311421 |
Remaining issues on two TAs for multi-DCI |
NEC |
| R1-2311433 |
Two TAs for multi-TRP/panel |
LG Electronics |
| R1-2311441 |
Maintenance on two TAs for multi-DCI |
Google |
| R1-2311475 |
Remaining issues on two TAs for multi-DCI |
CMCC |
| R1-2311613 |
Remaining issues on two TAs for multi-DCI |
NTT DOCOMO, INC. |
| R1-2311675 |
Two TAs for multi-DCI mTRP |
Apple |
| R1-2311719 |
Maintenance on two TAs for multi-DCI |
Sharp |
| R1-2311740 |
Maintenance of two TAs for UL multi-DCI multi-TRP operation |
Nokia, Nokia Shanghai Bell |
| R1-2311793 |
Remaining issues of two TAs for multi-DCI based multi-TRP operation |
Transsion Holdings |
| R1-2311830 |
Remaining details on two TAs for m-DCI |
Samsung |
| R1-2311926 |
Remaining issues on two TAs for multi-DCI |
Ruijie Network Co. Ltd |
| R1-2311972 |
Remaining issues on UL Tx timing management for MTRP |
MediaTek Inc. |
| R1-2312026 |
Supporting two TAs for multi-DCI based mTRP |
Qualcomm Incorporated |
| R1-2312329 |
Moderator Summary #1 on Two TAs for multi-DCI |
Moderator (Ericsson) |
| R1-2312473 |
Moderator Summary #2 on Two TAs for multi-DCI |
Moderator (Ericsson) |
| 8.1.2 |
CSI enhancement |
|
| R1-2310868 |
Maintenance of` CSI enhancement for coherent JT and mobility |
Huawei, HiSilicon |
| R1-2310921 |
Maintenance on Rel-18 CSI Enhancements |
InterDigital, Inc. |
| R1-2310949 |
Maintenance on CSI enhancement for high/medium UE velocities and CJT |
ZTE |
| R1-2311041 |
Maintenance on Rel-18 CSI enhancements |
Fujitsu |
| R1-2311085 |
Maintenance on CSI enhancement |
vivo |
| R1-2311157 |
Remaining issues on CSI enhancement |
Spreadtrum Communications |
| R1-2311215 |
Remaining issues on CSI enhancement for high/medium UE velocities and coherent JT |
OPPO |
| R1-2311316 |
Maintenance on CSI enhancement |
CATT |
| R1-2311363 |
Discussion of CSI enhancement for high speed UE and coherent JT |
Lenovo |
| R1-2311382 |
Maintenance on CSI enhancement for high/medium UE velocities and CJT |
xiaomi |
| R1-2311416 |
Remaining issues on CSI enhancement |
NEC |
| R1-2311434 |
Maintenance on Rel-18 CSI enhancement |
LG Electronics |
| R1-2311476 |
Remaining issues on CSI enhancement for high/medium UE velocities and CJT |
CMCC |
| R1-2311567 |
On CSI Enhancement |
Google |
| R1-2311614 |
Remaining issues on CSI enhancement |
NTT DOCOMO, INC. |
| R1-2311741 |
Maintenance of CSI enhancement for high/medium UE velocities and CJT |
Nokia, Nokia Shanghai Bell |
| R1-2311831 |
Moderator summary on Rel-18 CSI enhancements |
Moderator (Samsung) |
| R1-2311832 |
Remaining details on CSI enhancements |
Samsung |
| R1-2311927 |
Remaining issues on CSI enhancement |
Ruijie Network Co. Ltd |
| R1-2312027 |
Remaining issues and maintenance on Rel-18 CSI enhancement |
Qualcomm Incorporated |
| R1-2312095 |
Maintenance of CSI enhancements for Rel-18 NR MIMO evolution |
Ericsson |
| R1-2312195 |
CSI enhancements for medium UE velocities and coherent JT |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2312373 |
Moderator Summary#2 on Rel-18 CSI enhancements: Round 1 |
Moderator (Samsung) |
| R1-2312374 |
Moderator Summary on Tue offline session for Rel-18 CSI enhancements |
Moderator (Samsung) |
| R1-2312381 |
DRAFT LS to RAN2 on TDCP for Rel-18 MIMO |
Moderator (Samsung) |
| R1-2312382 |
LS to RAN2 on TDCP for Rel-18 MIMO |
RAN1, Samsung |
| 8.1.3.1 |
Increased number of orthogonal DMRS ports |
|
| R1-2310869 |
Maintenance of DMRS enhancement in Rel.18 |
Huawei, HiSilicon |
| R1-2310908 |
Maintenance on Rel-18 DMRS |
Ericsson |
| R1-2310922 |
Maintenance on Rel-18 DMRS Enhancements |
InterDigital, Inc. |
| R1-2310932 |
Discussions on the remaining issue on increased number of orthogonal DMRS ports |
New H3C Technologies Co., Ltd. |
| R1-2310950 |
Maintenance on DMRS enhancement for UL/DL MU-MIMO and 8 Tx UL SU-MIMO |
ZTE, China Telecom |
| R1-2311042 |
Discussion on remaining issues of PTRS for 8Tx UL transmission |
Fujitsu |
| R1-2311086 |
Maintenance on DMRS enhancements |
vivo |
| R1-2311158 |
Remaining issues on increased number of orthogonal DMRS ports |
Spreadtrum Communications |
| R1-2311216 |
Remaining issues on DMRS enhancement for Rel-18 MIMO |
OPPO |
| R1-2311317 |
Remaining issues on Rel-18 DMRS |
CATT |
| R1-2311364 |
Maintenance on increased number of orthogonal DMRS ports |
Lenovo |
| R1-2311477 |
Remaining issues on increased number of orthogonal DMRS ports |
CMCC |
| R1-2311568 |
On DMRS Enhancement |
Google |
| R1-2311615 |
Remaining issues on DMRS enhancements |
NTT DOCOMO, INC. |
| R1-2311676 |
Views on remaining issues for DMRS enhancement |
Apple |
| R1-2311720 |
Maintenance on increased number of orthogonal DMRS ports |
Sharp |
| R1-2311742 |
Maintenance of Rel-18 UL and DL DMRS Enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2311833 |
Remaining details on DMRS enhancements |
Samsung |
| R1-2311928 |
Remaining issues on increased number of orthogonal DMRS ports |
Ruijie Network Co. Ltd |
| R1-2312028 |
Design for increased number of orthogonal DMRS ports |
Qualcomm Incorporated |
| R1-2312266 |
FL summary#1 on DMRS |
Moderator (NTT DOCOMO) |
| R1-2312267 |
FL summary#2 on DMRS |
Moderator (NTT DOCOMO) |
| R1-2312268 |
FL summary#3 on DMRS |
Moderator (NTT DOCOMO) |
| 8.1.3.2 |
SRS enhancement targeting TDD CJT and 8 TX operation |
|
| R1-2310829 |
SRS enhancements for TDD CJT and 8TX operation |
FUTUREWEI |
| R1-2310870 |
Maintenance of SRS enhancement for TDD CJT and UL 8Tx operation in Rel-18 |
Huawei, HiSilicon |
| R1-2310923 |
Maintenance on Rel-18 SRS Enhancements |
InterDigital, Inc. |
| R1-2310951 |
Maintenance on SRS enhancement targeting TDD CJT and 8 TX operation |
ZTE |
| R1-2311087 |
Maintenance on SRS enhancements |
vivo |
| R1-2311217 |
Remaining issues on SRS enhancement targeting TDD CJT and 8 TX operation |
OPPO |
| R1-2311318 |
Remaining issues on SRS enhancement |
CATT |
| R1-2311365 |
Maintenance on SRS enhancement |
Lenovo |
| R1-2311383 |
Maintenance on SRS enhancements |
xiaomi |
| R1-2311478 |
Remaining issues on SRS enhancement targeting TDD CJT and 8 TX operation |
CMCC |
| R1-2311569 |
On SRS Enhancement |
Google |
| R1-2311616 |
Remaining issues on SRS enhancement |
NTT DOCOMO, INC. |
| R1-2311721 |
Maintenance on SRS enhancement targeting TDD CJT and 8 TX operation |
Sharp |
| R1-2311743 |
Maintenance of SRS enhancement for TDD CJT and 8Tx operation |
Nokia, Nokia Shanghai Bell |
| R1-2311834 |
Remaining details on SRS enhancements |
Samsung |
| R1-2311883 |
Remaining issues on SRS enhancement targeting TDD CJT and 8 TX operation |
KDDI Corporation |
| R1-2311929 |
Maintenance on SRS enhancement targeting TDD CJT and 8 TX operation |
Ruijie Network Co. Ltd |
| R1-2312029 |
SRS enhancement for TDD CJT and 8 Tx operation |
Qualcomm Incorporated |
| R1-2312180 |
Maintenance on SRS enhancements targeting TDD CJT and 8 TX operation |
Ericsson |
| R1-2312316 |
FL Summary #1 on SRS enhancements |
Moderator (FUTUREWEI) |
| R1-2312317 |
FL Summary #2 on SRS enhancements |
Moderator (FUTUREWEI) |
| R1-2312318 |
FL Summary #3 on SRS enhancements |
Moderator (FUTUREWEI) |
| 8.1.4.1 |
UL precoding indication for multi-panel transmission |
|
| R1-2310871 |
Maintenance on UL precoding indication for multi-panel transmission |
Huawei, HiSilicon |
| R1-2310924 |
Maintenance on Rel-18 MPUE Uplink Transmission |
InterDigital, Inc. |
| R1-2310952 |
Maintenance on UL precoding indication for multi-panel transmission |
ZTE |
| R1-2311043 |
Remaining issues on UL precoding indication for multi-panel transmission |
Fujitsu |
| R1-2311088 |
Maintenance on UL precoding indication for multi-panel transmission |
vivo |
| R1-2311159 |
Remaining issues on UL precoding indication for multi-panel transmission |
Spreadtrum Communications |
| R1-2311218 |
Remaining issues of UL precoding indication for multi-panel transmission |
OPPO |
| R1-2311319 |
Remaining issues on UL precoding indication for multi-panel transmission |
CATT |
| R1-2311366 |
Maintenance on UL precoding indication for multi-panel transmission |
Lenovo |
| R1-2311384 |
Maintenance on multi-panel uplink transmission |
xiaomi |
| R1-2311422 |
Remaining issues on UL precoding indication for multi-panel transmission |
NEC |
| R1-2311479 |
Remaining issues on UL precoding indication for multi-panel transmission |
CMCC |
| R1-2311523 |
Remaining Issues on UL Precoding for Multi-panel Transmission |
Panasonic |
| R1-2311570 |
On Simultaneous Multi-Panel Transmission |
Google |
| R1-2311617 |
Remaining issues on multi-panel transmission |
NTT DOCOMO, INC. |
| R1-2311657 |
UL precoding indication for multi-panel transmission |
Intel Corporation |
| R1-2311677 |
Remaining issues on multi-panel simultaneous transmissions |
Apple |
| R1-2311726 |
Maintenance on UL multi-panel transmission |
Sharp |
| R1-2311734 |
Remaining issues on UL precoding indication for multi-panel transmission |
Langbo |
| R1-2311744 |
Maintenance of precoder Indication for Multi-Panel UL Transmission |
Nokia, Nokia Shanghai Bell |
| R1-2311794 |
Remaining issues of UL precoding indication for multi-panel transmission |
Transsion Holdings |
| R1-2311835 |
Remaining details on UL precoding indication for STxMP |
Samsung |
| R1-2311930 |
Remaining issues on UL precoding indication for multi-panel transmission |
Ruijie Network Co. Ltd |
| R1-2311973 |
Remaining issues on simultaneous UL transmission across multi-panel |
MediaTek Inc. |
| R1-2312006 |
Remaining issues on UL precoding indication for multi-panel transmission |
Hyundai Motor Company |
| R1-2312030 |
Simultaneous multi-panel transmission |
Qualcomm Incorporated |
| R1-2312194 |
Maintenance on UL precoding indication for multi-panel transmission |
Ericsson |
| R1-2312255 |
Summary #1 on Rel-18 STxMP |
Moderator (OPPO) |
| R1-2312256 |
Summary #2 on Rel-18 STxMP |
Moderator (OPPO) |
| R1-2312257 |
Summary #3 on Rel-18 STxMP |
Moderator (OPPO) |
| 8.1.4.2 |
SRI/TPMI enhancement for enabling 8 TX UL transmission |
|
| R1-2310925 |
Maintenance on Rel-18 8TX UE Operation |
InterDigital, Inc. |
| R1-2310926 |
FL Summary SRI/TPMI Enhancements; First Round |
Moderator (InterDigital, Inc.) |
| R1-2310927 |
FL Summary SRI/TPMI Enhancements; Second Round |
Moderator (InterDigital, Inc.) |
| R1-2310928 |
Summary of Discussion and Agreements in RAN1#114bis |
Moderator (InterDigital, Inc.) |
| R1-2310953 |
Maintenance on SRI/TPMI enhancement for enabling 8 TX UL transmission |
ZTE |
| R1-2311044 |
Discussion on remaining issues for 8Tx UL transmission |
Fujitsu |
| R1-2311089 |
Maintenance on enabling 8 TX UL transmission |
vivo |
| R1-2311160 |
Remaining issues on SRI/TPMI enhancement for enabling 8 TX UL transmission |
Spreadtrum Communications |
| R1-2311219 |
Remaining issues on SRI TPMI enhancement for 8 TX UL transmission |
OPPO |
| R1-2311320 |
Discussion of remaining issues on enhancement of SRI/TPMI for 8TX UL transmission |
CATT |
| R1-2311367 |
Maintenance on SRI/TPMI enhancement for enabling 8TX UL transmission |
Lenovo |
| R1-2311385 |
Enhancements on 8Tx uplink transmission |
xiaomi |
| R1-2311417 |
Remaining issues on SRI/TPMI enhancement |
NEC |
| R1-2311435 |
SRI/TPMI enhancement for enabling 8 TX UL transmission |
LG Electronics |
| R1-2311480 |
Remaining issues on SRI/TPMI enhancement for enabling 8 TX UL transmission |
CMCC |
| R1-2311571 |
On SRI/TPMI Indication for 8Tx Transmission |
Google |
| R1-2311590 |
Remaining issues on Full Power Mode for 8 TX UL Transmission |
FGI |
| R1-2311618 |
Remaining issues on 8 TX UL transmission |
NTT DOCOMO, INC. |
| R1-2311678 |
Maintenance on SRI/TPMI enhancement for enabling 8 TX UL transmission |
Apple |
| R1-2311727 |
Maintenance on 8 TX UL transmission |
Sharp |
| R1-2311745 |
Maintenance of UL enhancements for enabling 8Tx UL transmission |
Nokia, Nokia Shanghai Bell |
| R1-2311836 |
Remaining details on TPMI/SRI enhancements for 8Tx UL transmission |
Samsung |
| R1-2311931 |
Maintenance on SRI/TPMI enhancement for enabling 8 TX UL transmission |
Ruijie Network Co. Ltd |
| R1-2311944 |
8 Tx SRI/TPMI Corrections |
Ericsson |
| R1-2312155 |
Maintenance of SRI/TPMI enhancement for enabling 8 TX UL transmission |
Huawei, HiSilicon |
| R1-2312169 |
Remaining issues on SRI/TPMI enhancement for enabling 8 TX UL transmission |
KDDI Corporation |
| R1-2312561 |
[Draft] LS On Relative Phase/Power Error Requirements within Port Groups for 8TX UE |
InterDigital |
| R1-2312566 |
LS On Relative Phase/Power Error Requirements within Port Groups for 8TX UE |
RAN1, InterDigital |
| 8.2 |
Maintenance on NR Sidelink Evolution |
|
| R1-2311235 |
Higher layer parameters list for Rel-18 NR sidelink evolution WI |
OPPO, Huawei, HiSilicon, LG Electronics |
| R1-2312503 |
Session notes for 8.2 (Maintenance on NR sidelink evolution) |
Ad-Hoc Chair (Huawei) |
| R1-2312703 |
RAN1 agreements for Rel-18 NR Sidelink Evolution |
Rapporteur (OPPO) |
| 8.2.1.1 |
Channel access mechanism |
|
| R1-2310811 |
Remaining issues for Channel Access Mechanism for SL-U |
Nokia, Nokia Shanghai Bell |
| R1-2310824 |
Maintenance of sidelink unlicensed channel access |
FUTUREWEI |
| R1-2310851 |
Maintenance of channel access mechanism and resource allocation for sidelink operation over unlicensed spectrum |
Huawei, HiSilicon |
| R1-2311090 |
Remaining issues on channel access mechanism for sidelink on unlicensed spectrum |
vivo |
| R1-2311161 |
Remaining issues on channel access mechanism for sidelink on unlicensed spectrum |
Spreadtrum Communications |
| R1-2311236 |
On maintenance of SL-U channel access mechanism and resource allocation |
OPPO |
| R1-2311336 |
Maintenance on channel access mechanism for sidelink on unlicensed spectrum |
CATT, CICTCI |
| R1-2311400 |
Remaining details on SL-U channel access mechanism |
xiaomi |
| R1-2311414 |
Remaining Issues on Channel Access of Sidelink on Unlicensed Spectrum |
NEC |
| R1-2311515 |
Discussion on channel access mechanism for SL-U |
ZTE, Sanechips |
| R1-2311525 |
Remaining issues on channel access mechanism for sidelink on unlicensed spectrum |
Sony |
| R1-2311563 |
Sidelink channel access on unlicensed spectrum |
Panasonic |
| R1-2311588 |
Remaining issues on channel access mechanism for sidelink on unlicensed spectrum |
Lenovo |
| R1-2311619 |
Remaining issues on channel access mechanism in SL-U |
NTT DOCOMO, INC. |
| R1-2311679 |
On remaining issue for sidelink channal access for unlicensed spectrum |
Apple |
| R1-2311751 |
Remaining issues on channel access mechanism for sidelink on unlicensed spectrum |
ETRI |
| R1-2311766 |
Remaining issues on Channel access mechanism for NR sidelink evolution |
Sharp |
| R1-2311795 |
Remaining issues of channel access mechanism for sidelink in unlicensed spectrum |
Transsion Holdings |
| R1-2311837 |
Remaining issues on channel access mechanism |
Samsung |
| R1-2311884 |
Remaining issues for channel access on SL-U |
InterDigital, Inc. |
| R1-2311975 |
Discussion on remaining issue for channel access mechanism |
MediaTek Inc. |
| R1-2312031 |
Channel Access Mechanism for Sidelink on Unlicensed Spectrum |
Qualcomm Incorporated |
| R1-2312121 |
Remaining issues on channel access mechanism for sidelink on unlicensed spectrum |
LG Electronics |
| R1-2312171 |
Remaining issues on channel access mechanism for SL-U |
WILUS Inc. |
| R1-2312248 |
FL summary #1 for AI 8.2.1.1: SL-U channel access mechanism |
Moderator (OPPO) |
| R1-2312249 |
FL summary #2 for AI 8.2.1.1: SL-U channel access mechanism |
Moderator (OPPO) |
| R1-2312250 |
FL summary #3 for AI 8.2.1.1: SL-U channel access mechanism |
Moderator (OPPO) |
| R1-2312251 |
FL summary #4 for AI 8.2.1.1: SL-U channel access mechanism |
Moderator (OPPO) |
| R1-2312252 |
FL summary #5 for AI 8.2.1.1: SL-U channel access mechanism |
Moderator (OPPO) |
| R1-2312253 |
FL summary #6 for AI 8.2.1.1: SL-U channel access mechanism |
Moderator (OPPO) |
| R1-2312254 |
FL summary for AI 8.2.1.1: SL-U channel access mechanism (EOM) |
Moderator (OPPO) |
| R1-2312666 |
[Draft] LS on re-evaluation and pre-emption checking for MCSt |
CATT, CICTCI |
| R1-2312667 |
LS on re-evaluation and pre-emption checking for MCSt |
RAN1, CATT, CICTCI |
| 8.2.1.2 |
Physical channel design framework |
|
| R1-2310812 |
Remaining issues for Physical Channel Design Framework for SL-U |
Nokia, Nokia Shanghai Bell |
| R1-2310852 |
Maintenance of physical channel design for sidelink operation over unlicensed spectrum |
Huawei, HiSilicon |
| R1-2310969 |
Remaining issues on physical channel design of sidelink on unlicensed spectrum |
Quectel |
| R1-2311091 |
Remaining issues on physical channel design framework for sidelink on unlicensed spectrum |
vivo |
| R1-2311162 |
Remaining issues on Physical channel design for sidelink on unlicensed spectrum |
Spreadtrum Communications |
| R1-2311237 |
On maintenance of SL-U PHY channel designs and procedures |
OPPO |
| R1-2311337 |
Maintenance on physical channel design framework for sidelink on unlicensed spectrum |
CATT, CICTCI |
| R1-2311401 |
Remaining details on SL-U physical channel structures and procedures |
xiaomi |
| R1-2311425 |
Remaining issues on physical channel design framework |
NEC |
| R1-2311516 |
Discussion on physical layer structures and procedures for SL-U |
ZTE, Sanechips |
| R1-2311565 |
Physical channel design for sidelink on unlicensed spectrum |
Panasonic |
| R1-2311589 |
Remaining issues on physical layer design framework for sidelink on unlicensed spectrum |
Lenovo |
| R1-2311620 |
Remaining issues on channel design framework in SL-U |
NTT DOCOMO, INC. |
| R1-2311680 |
On Remaining Issues of Sidelink Physical Channel Design Framework for Unlicensed Spectrum |
Apple |
| R1-2311752 |
Remaining issues on physical channel design framework for SL-U |
ETRI |
| R1-2311767 |
Remaining issues on physical channel design framework for NR sidelink evolution on unlicensed spectrum |
Sharp |
| R1-2311796 |
Remaining issues of physical channel design for sidelink in unlicensed spectrum |
Transsion Holdings |
| R1-2311838 |
Remaining issues on physical channel design framework |
Samsung |
| R1-2311885 |
Remaining issues for SL U physical layer design |
InterDigital, Inc. |
| R1-2311976 |
Discussion on remaining issue for physical channel design framework |
MediaTek Inc. |
| R1-2312032 |
Physical Channel Design for Sidelink on Unlicensed Spectrum |
Qualcomm Incorporated |
| R1-2312122 |
Remaining issues on physical channel design framework for sidelink on unlicensed spectrum |
LG Electronics |
| R1-2312135 |
Discussion on channel design for SL-U |
ASUSTeK |
| R1-2312172 |
Remaining issues on PHY channel design for SL-U |
WILUS Inc. |
| R1-2312312 |
Discussion on physical layer structures and procedures for SL-U |
ZTE, Sanechips |
| R1-2312324 |
FL summary#1 for AI 8.2.1.2 SL-U physical channel design framework |
Moderator (Huawei) |
| R1-2312325 |
FL summary#2 for AI 8.2.1.2 SL-U physical channel design framework |
Moderator (Huawei) |
| R1-2312326 |
FL summary#3 for AI 8.2.1.2 SL-U physical channel design framework |
Moderator (Huawei) |
| R1-2312327 |
FL summary#4 for AI 8.2.1.2 SL-U physical channel design framework |
Moderator (Huawei) |
| R1-2312328 |
FL summary#5 for AI 8.2.1.2 SL-U physical channel design framework |
Moderator (Huawei) |
| R1-2312531 |
FL summary#6 for AI 8.2.1.2 SL-U physical channel design framework |
Moderator (Huawei) |
| R1-2312532 |
FL summary#7 for AI 8.2.1.2 SL-U physical channel design framework |
Moderator (Huawei) |
| 8.2.2 |
Co-channel coexistence for LTE sidelink and NR sidelink |
|
| R1-2310813 |
Remaining issues for Co-channel Coexistence for LTE Sidelink and NR Sidelink |
Nokia, Nokia Shanghai Bell |
| R1-2310853 |
Maintenance of co-channel coexistence for LTE sidelink and NR sidelink |
Huawei, HiSilicon |
| R1-2311092 |
Remaining issues on co-channel coexistence for LTE sidelink and NR sidelink |
vivo |
| R1-2311238 |
On maintenance of co-channel coexistence for LTE and NR SL |
OPPO |
| R1-2311338 |
Maintenance on co-channel coexistence for LTE sidelink and NR sidelink |
CATT, CICTCI |
| R1-2311517 |
Maintenance on co-channel coexistence for LTE sidelink and NR sidelink |
ZTE, Sanechips |
| R1-2311621 |
Maintenance on co-channel coexistence for LTE sidelink and NR sidelink |
NTT DOCOMO, INC. |
| R1-2311768 |
Remaining issues on co-channel coexistence for LTE sidelink and NR sidelink |
Sharp |
| R1-2311839 |
Remaining issues on co-channel coexistence for LTE sidelink and NR sidelink |
Samsung |
| R1-2311886 |
Remaining issues for Co-channel coexistence between LTE sidelink and NR sidelink |
InterDigital, Inc. |
| R1-2312259 |
FL Summary #1 for AI 8.2.2: Co-channel coexistence for LTE sidelink and NR sidelink |
Moderator (LG Electronics) |
| R1-2312260 |
FL Summary #2 for AI 8.2.2: Co-channel coexistence for LTE sidelink and NR sidelink |
Moderator (LG Electronics) |
| R1-2312261 |
FL Summary #3 for AI 8.2.2: Co-channel coexistence for LTE sidelink and NR sidelink |
Moderator (LG Electronics) |
| 8.2.3 |
Sidelink CA operation |
|
| R1-2310814 |
Remaining issues for Sidelink Carrier Aggregation for NR |
Nokia, Nokia Shanghai Bell |
| R1-2310854 |
Maintenance of sidelink CA operation |
Huawei, HiSilicon |
| R1-2311093 |
Remaining issues on Rel-18 sidelink CA |
vivo |
| R1-2311239 |
On maintenance of carrier aggregation in NR Sidelink evolution |
OPPO |
| R1-2311518 |
Remaining issues for sidelink CA operation |
ZTE, Sanechips |
| R1-2311681 |
On Remaining Issue of Sidelink CA Operation |
Apple |
| R1-2311753 |
Remaining issues on sidelink CA operation |
ETRI |
| R1-2311769 |
Remaining issues on Carrier Aggregation for NR sidelink evolution |
Sharp |
| R1-2311840 |
Remaining issues on sidelink CA operation |
Samsung |
| R1-2311887 |
Remaining issues for Sidelink CA operation |
InterDigital, Inc. |
| R1-2312262 |
FL Summary #1 for AI 8.2.3: Sidelink CA operation |
Moderator (LG Electronics) |
| R1-2312263 |
FL Summary #2 for AI 8.2.3: Sidelink CA operation |
Moderator (LG Electronics) |
| R1-2312264 |
FL Summary #3 for AI 8.2.3: Sidelink CA operation |
Moderator (LG Electronics) |
| 8.3 |
Maintenance on Expanded and Improved NR Positioning |
|
| R1-2311141 |
Higher layer parameters for Rel-18 Expanded and Improved NR Positioning |
Rapporteur (Intel Corporation) |
| R1-2312380 |
Moderator Summary #1 on Reply LS on request for clarifications on RedCap positioning, carrier phase positioning, and bandwidth aggregation for positioning |
Moderator (Nokia) |
| R1-2312432 |
Moderator Summary #2 on Reply LS on request for clarifications on RedCap positioning, carrier phase positioning, and bandwidth aggregation for positioning |
Moderator (Nokia) |
| R1-2312433 |
Draft Reply LS on request for clarifications on RedCap positioning, carrier phase positioning, and bandwidth aggregation for positioning |
Moderator (Nokia) |
| R1-2312434 |
Reply LS on request for clarifications on RedCap positioning, carrier phase positioning, and bandwidth aggregation for positioning |
RAN1, Nokia |
| R1-2312504 |
Session notes for 8.3 (Maintenance on expanded and improved NR positioning) |
Ad-Hoc Chair (Huawei) |
| R1-2312690 |
RAN1 agreements for Rel-18 WI on Expanded and Improved NR Positioning |
Rapporteur (Intel Corporation) |
| 8.3.1.1 |
SL positioning reference signal |
|
| R1-2310815 |
Remaining issues for design of SL positioning reference signal SL PRS |
Nokia, Nokia Shanghai Bell |
| R1-2310836 |
Maintenance of SL-PRS |
Huawei, HiSilicon |
| R1-2311094 |
Remaining issues on SL positioning reference signal |
vivo |
| R1-2311163 |
Remaining issues on SL positioning reference signal |
Spreadtrum Communications |
| R1-2311240 |
Remaining issues on SL positioning reference signal |
OPPO |
| R1-2311339 |
Maintenance issues on SL positioning reference signal |
CATT, CICTCI |
| R1-2311402 |
Remaining details on SL positioning reference signal |
xiaomi |
| R1-2311430 |
Remaining issues on SL positioning reference signal |
NEC |
| R1-2311456 |
Maintenance on SL positioning reference signal |
ZTE |
| R1-2311559 |
Maintenance on sidelink positioning reference signal |
ASUSTeK |
| R1-2311595 |
Remaining issues on SL-PRS design and power control for SL-PRS |
InterDigital, Inc. |
| R1-2311682 |
Remaining Issues On SL positioning reference signal |
Apple |
| R1-2311747 |
Remaining issues on SL positioning reference signal |
Sharp |
| R1-2311841 |
Maintenance on SL Positioning Reference Signal |
Samsung |
| R1-2311932 |
Remaining issues on SL positioning reference signal |
Ruijie Network Co. Ltd |
| R1-2312033 |
Reference Signal Design for SL Positioning |
Qualcomm Incorporated |
| R1-2312092 |
Maintenance for SL-PRS design |
MediaTek Korea Inc. |
| R1-2312123 |
Remaining issues on SL positioning reference signal |
LG Electronics |
| R1-2312185 |
Remaining issues on SL positioning reference signal design |
Ericsson |
| R1-2312295 |
FL summary #1 on SL positioning reference signal |
Moderator (Intel Corporation) |
| R1-2312296 |
FL summary #2 on SL positioning reference signal |
Moderator (Intel Corporation) |
| R1-2312297 |
FL summary #3 on SL positioning reference signal |
Moderator (Intel Corporation) |
| 8.3.1.2 |
Measurements and reporting for SL positioning |
|
| R1-2310816 |
Remaining issues for measurements and reporting for SL positioning |
Nokia, Nokia Shanghai Bell |
| R1-2310837 |
Maintenance of SL measurements |
Huawei, HiSilicon |
| R1-2311095 |
Remaining issues on measurements and reporting for SL positioning |
vivo |
| R1-2311142 |
Remaining issues on SL Positioning Measurements and Reporting |
Intel Corporation |
| R1-2311164 |
Remaining issues on measurements and reporting for SL positioning |
Spreadtrum Communications |
| R1-2311241 |
Remaining issues on measurements and reporting for SL positioning |
OPPO |
| R1-2311340 |
Maintenance issues on measurements and reporting for SL positioning |
CATT, CICTCI |
| R1-2311457 |
Maintenance on SL positioning measurements and reporting |
ZTE |
| R1-2311481 |
Maintenance on measurements and reporting for SL positioning |
CMCC |
| R1-2311596 |
Remaining issues on measurement and reporting for SL positioning |
InterDigital, Inc. |
| R1-2311683 |
Remaining Issues On Measurements and reporting for SL positioning |
Apple |
| R1-2311842 |
Maintenance on Measurements and Reporting for SL Positioning |
Samsung |
| R1-2311949 |
SL Pos. Measurement and Reporting Maintenance |
Lenovo |
| R1-2312034 |
Measurements and Reporting for SL Positioning |
Qualcomm Incorporated |
| R1-2312124 |
Remaining issues on measurements and reporting for SL positioning |
LG Electronics |
| R1-2312186 |
Remaining issues on measurements and reporting for SL positioning |
Ericsson |
| R1-2312416 |
Summary #1 on Measurements and reporting for SL positioning |
Moderator (vivo) |
| R1-2312417 |
Summary #2 on Measurements and reporting for SL positioning |
Moderator (vivo) |
| R1-2312418 |
Summary #3 on Measurements and reporting for SL positioning |
Moderator (vivo) |
| 8.3.1.3 |
Resource allocation for SL positioning reference signal |
|
| R1-2310817 |
Remaining issues for resource allocation for SL positioning reference signal SL PRS |
Nokia, Nokia Shanghai Bell |
| R1-2310838 |
Maintenance of SL-PRS resource allocation |
Huawei, HiSilicon |
| R1-2311096 |
Remaining issues on resource allocation for SL positioning reference signal |
vivo |
| R1-2311143 |
Remaining issues on resource allocation for SL positioning |
Intel Corporation |
| R1-2311165 |
Remaining issues on resource allocation for SL positioning reference signal |
Spreadtrum Communications |
| R1-2311242 |
Remaining issues on resource allocation for SL positioning reference signal |
OPPO |
| R1-2311341 |
Maintenance issues on resource allocation for SL positioning reference signal |
CATT, CICTCI |
| R1-2311403 |
Remaining details on resource allocation for SL positioning reference signal |
xiaomi |
| R1-2311431 |
Remaining issues on resource allocation for SL positioning reference signal |
NEC |
| R1-2311458 |
Maintenance on resource allocation for SL positioning reference signal |
ZTE |
| R1-2311482 |
Maintenance on resource allocation for SL positioning reference signal |
CMCC |
| R1-2311544 |
Remaining issues on resource allocation for SL PRS |
China Telecom |
| R1-2311560 |
Maintenance on Resource allocation for SL PRS |
ASUSTeK |
| R1-2311597 |
Remaining issues on SL PRS resource allocation |
InterDigital, Inc. |
| R1-2311684 |
Remaining Issues On Resource allocation for SL positioning reference signal |
Apple |
| R1-2311748 |
Remaining issues on resource allocation for SL positioning reference signal |
Sharp |
| R1-2311843 |
Maintenance on Resource Allocation for SL Positioning Reference Signal |
Samsung |
| R1-2312035 |
Resource Allocation for SL-PRS |
Qualcomm Incorporated |
| R1-2312125 |
Remaining issues on resource allocation for SL positioning reference signal |
LG Electronics |
| R1-2312157 |
Remaining issues on resource allocation for SL positioning reference signal |
CEWiT |
| R1-2312187 |
Remaining issues on resource allocation for SL positioning reference signal |
Ericsson |
| R1-2312293 |
Remaining issues on resource allocation for SL positioning |
Intel Corporation |
| R1-2312420 |
Moderator Summary #0 on resource allocation for SL PRS |
Moderator (Qualcomm) |
| R1-2312472 |
Moderator Summary #1 on resource allocation for SL PRS |
Moderator (Qualcomm) |
| R1-2312629 |
Draft LS on the request for specific SL PRS resource characteristic(s)/SL-PRS resource configuration |
Qualcomm Incorporated |
| R1-2312630 |
LS on the request for specific SL PRS resource characteristic(s)/SL-PRS resource configuration |
RAN1, Qualcomm Incorporated |
| 8.3.2 |
NR DL and UL carrier phase positioning |
|
| R1-2310839 |
Maintenance of CPP |
Huawei, HiSilicon |
| R1-2310978 |
Remaining issues on NR DL and UL carrier phase positioning |
Nokia, Nokia Shanghai Bell |
| R1-2311097 |
Remaining issues on carrier phase positioning |
vivo |
| R1-2311144 |
Maintenance for DL and UL Carrier Phase Positioning |
Intel Corporation |
| R1-2311166 |
Remaining issues on NR DL and UL carrier phase positioning |
Spreadtrum Communications |
| R1-2311224 |
Remaining Issues of NR carrier phase positioning |
OPPO |
| R1-2311342 |
Maintenance issues on NR DL and UL carrier phase positioning |
CATT |
| R1-2311404 |
Remaining issues on NR DL and UL carrier phase positioning |
xiaomi |
| R1-2311459 |
Maintenance on carrier phase positioning |
ZTE |
| R1-2311598 |
Remaining issues for positioning based on NR carrier phase measurement |
InterDigital, Inc. |
| R1-2311622 |
Remaining issues on NR DL and UL carrier phase positioning |
NTT DOCOMO, INC. |
| R1-2311685 |
Remaining Issues On NR DL and UL carrier phase positioning |
Apple |
| R1-2311844 |
Maintenance on NR DL and UL Carrier Phase Positioning |
Samsung |
| R1-2311911 |
Remaining issues on carrier phase positioning in NR |
LG Electronics |
| R1-2311950 |
CPP Maintenance Discussion |
Lenovo |
| R1-2312036 |
NR Carrier Phase Positioning |
Qualcomm Incorporated |
| R1-2312119 |
Remaining issues on NR DL and UL carrier phase positioning |
Ruijie Network Co. Ltd |
| R1-2312188 |
Remaining issues on NR DL and UL carrier phase positioning |
Ericsson |
| R1-2312269 |
FL Summary #1 for maintenance on NR DL and UL carrier phase positioning |
Moderator (CATT) |
| R1-2312270 |
FL Summary #2 for maintenance on NR DL and UL carrier phase positioning |
Moderator (CATT) |
| R1-2312271 |
FL Summary #3 for maintenance on NR DL and UL carrier phase positioning |
Moderator (CATT) |
| R1-2312392 |
Draft reply LS on CPP |
CATT |
| R1-2312393 |
Reply LS on CPP |
RAN1, CATT |
| 8.3.3 |
LPHAP (Low Power High Accuracy Positioning) |
|
| R1-2310840 |
Maintenance of LPHAP |
Huawei, HiSilicon |
| R1-2310979 |
Remaining issues on LPHAP |
Nokia, Nokia Shanghai Bell |
| R1-2311098 |
Remaining issues on low power high accuracy positioning |
vivo |
| R1-2311226 |
Remaining issues of low power high accuracy positioning |
OPPO |
| R1-2311343 |
Maintenance issues on low power high accuracy positioning |
CATT |
| R1-2311419 |
Remaining issues on low power high accuracy positioning |
NEC |
| R1-2311460 |
Maintenance on low power high accuracy positioning |
ZTE |
| R1-2311483 |
Maintenance on low power high accuracy positioning |
CMCC |
| R1-2311599 |
Remaining issues on Low Power High Accuracy Positioning (LPHAP) |
InterDigital, Inc. |
| R1-2311623 |
Remaining issues on low power high accuracy positioning |
NTT DOCOMO, INC. |
| R1-2311845 |
Maintenance on Low Power High Accuracy Positioning |
Samsung |
| R1-2312037 |
Discussion on LPHAP Positioning |
Qualcomm Incorporated |
| R1-2312105 |
Remaining Issues on Low Power High Accuracy Positioning |
Quectel |
| R1-2312189 |
Remaining issues on Low Power High Accuracy Positioning |
Ericsson |
| R1-2312302 |
Summary #1 for low power high accuracy positioning |
Moderator (Huawei, CMCC) |
| R1-2312303 |
Summary #2 for low power high accuracy positioning |
Moderator (Huawei, CMCC) |
| 8.3.4 |
Bandwidth aggregation for positioning measurements |
|
| R1-2310841 |
Maintenance of positioning with BW aggregation |
Huawei, HiSilicon, China Telecom, China Unicom |
| R1-2310980 |
Remaining issues on bandwidth aggregation for positioning measurements |
Nokia, Nokia Shanghai Bell |
| R1-2311099 |
Remaining issues on bandwidth aggregation for positioning measurements |
vivo |
| R1-2311145 |
Maintenance for Bandwidth Aggregation for Positioning |
Intel Corporation |
| R1-2311167 |
Remaining issues on bandwidth aggregation for positioning measurements |
Spreadtrum Communications |
| R1-2311225 |
Remaining Issues of bandwidth aggregation for positioning measurement |
OPPO |
| R1-2311344 |
Maintenance issues on bandwidth aggregation for positioning measurements |
CATT |
| R1-2311405 |
Remaining issues on bandwidth aggregation for positioning measurement |
xiaomi |
| R1-2311461 |
Maintenance on BW aggregation for positioning |
ZTE |
| R1-2311464 |
Summary #1 for BW aggregation positioning |
Moderator (ZTE) |
| R1-2311465 |
Summary #2 for BW aggregation positioning |
Moderator (ZTE) |
| R1-2311484 |
Maintenance on BW aggregation for positioning measurements |
CMCC |
| R1-2311600 |
Remaining issues on bandwidth aggregation for positioning measurements |
InterDigital, Inc. |
| R1-2311624 |
Remaining issues on bandwidth aggregation for positioning measurements |
NTT DOCOMO, INC. |
| R1-2311686 |
Remaining Issues On Bandwidth aggregation for positioning measurements |
Apple |
| R1-2311846 |
Maintenance on Bandwidth Aggregation for Positioning Measurements |
Samsung |
| R1-2311912 |
Remaining issues on Bandwidth aggregation for positioning measurements |
LG Electronics |
| R1-2312038 |
Discussion on Bandwidth aggregation for Positioning |
Qualcomm Incorporated |
| R1-2312093 |
Maintenance for bandwidth aggregation for positioning |
MediaTek Korea Inc. |
| R1-2312190 |
Remaining issues on bandwidth aggregation for positioning measurements |
Ericsson |
| R1-2312394 |
Draft Reply LS on SRS and PRS bandwidth aggregation for positioning |
Moderator (ZTE) |
| R1-2312395 |
Reply LS on SRS and PRS bandwidth aggregation for positioning |
RAN1, ZTE |
| R1-2312396 |
Summary #3 for BW aggregation positioning |
Moderator (ZTE) |
| 8.3.5 |
Positioning for RedCap UEs |
|
| R1-2310823 |
On remaining open issues and maintenance for RedCap UE Positioning |
FUTUREWEI |
| R1-2310842 |
Maintenance of RedCap positioning |
Huawei, HiSilicon |
| R1-2310981 |
Remaining issues on Positioning for RedCap UEs |
Nokia, Nokia Shanghai Bell |
| R1-2310989 |
Remaining issues of positioning for RedCap UEs |
New H3C Technologies Co., Ltd. |
| R1-2311100 |
Remaining issues on positioning for RedCap UEs |
vivo |
| R1-2311146 |
Remaining details of Positioning for RedCap Ues |
Intel Corporation |
| R1-2311168 |
Remaining issues on positioning for RedCap UEs |
Spreadtrum Communications |
| R1-2311227 |
Remaining issues of positioning for RedCap UEs |
OPPO |
| R1-2311345 |
Maintenance issues on positioning for RedCap UEs |
CATT |
| R1-2311418 |
Remaining issues on positioning for RedCap UEs |
NEC |
| R1-2311462 |
Maintenance on Positioning for RedCap UEs |
ZTE |
| R1-2311485 |
Maintenance on RedCap UE positioning |
CMCC |
| R1-2311601 |
Remaining issues on positioning for RedCap UEs |
InterDigital, Inc. |
| R1-2311625 |
Remaining issues on positioning for RedCap UEs |
NTT DOCOMO, INC. |
| R1-2311687 |
Remaining Issues On Positioning for RedCap UEs |
Apple |
| R1-2311847 |
Maintenance on Positioning for RedCap UEs |
Samsung |
| R1-2311913 |
Remaining issues on positioning support for RedCap UEs |
LG Electronics |
| R1-2312039 |
Maintenance for Positioning for Reduced Capabilities UEs |
Qualcomm Incorporated |
| R1-2312094 |
Maintenance for RedCap UE for positioning |
MediaTek Korea Inc. |
| R1-2312191 |
Remaining issues on positioning for RedCap Ues |
Ericsson |
| R1-2312342 |
Feature Lead summary #1 for Positioning for RedCap UEs |
Moderator (Ericsson) |
| R1-2312343 |
Feature Lead summary #2 for Positioning for RedCap UEs |
Moderator (Ericsson) |
| R1-2312344 |
Feature Lead summary #3 for Positioning for RedCap UEs |
Moderator (Ericsson) |
| R1-2312345 |
Feature Lead summary #4 for Positioning for RedCap UEs |
Moderator (Ericsson) |
| R1-2312652 |
Feature Lead summary #5 for Positioning for RedCap UEs |
Moderator (Ericsson) |
| R1-2312653 |
Feature Lead final summary for Positioning for RedCap UEs |
Moderator (Ericsson) |
| 8.4 |
Maintenance on Enhanced Support of Reduced Capability NR device |
|
| R1-2312283 |
RAN1 agreements for Rel-18 NR RedCap |
Rapporteur (Ericsson) |
| R1-2312505 |
Session notes for 8.4 (Maintenance on enhanced support of reduced capability NR device) |
Ad-Hoc Chair (Huawei) |
| 8.4.1 |
UE complexity reduction |
|
| R1-2310820 |
Maintenance of R18 RedCap |
FUTUREWEI |
| R1-2310857 |
Maintenance on Rel-18 RedCap |
Huawei, HiSilicon |
| R1-2310992 |
Discussion on further UE complexity reduction |
ZTE, Sanechips |
| R1-2311000 |
Maintenance on UE complexity reduction for eRedCap |
Panasonic |
| R1-2311101 |
Remaining issues on further UE complexity reduction |
vivo |
| R1-2311169 |
Remaining issues on enhanced support of RedCap devices |
Spreadtrum Communications |
| R1-2311262 |
Further consideration on specification for Rel-18 RedCap |
OPPO |
| R1-2311346 |
Remaining issues of Rel-18 RedCap |
CATT |
| R1-2311406 |
Discussion on further complexity reduction for eRedCap UEs |
xiaomi |
| R1-2311486 |
Maintenance on further complexity reduction for eRedCap |
CMCC |
| R1-2311541 |
Maintenance on Rel-18 RedCap UE |
NEC |
| R1-2311545 |
Remaining issues on UE complexity reduction for eRedCap UEs |
China Telecom |
| R1-2311626 |
Maintenance on further UE complexity reduction for eRedCap |
NTT DOCOMO, INC. |
| R1-2311688 |
Further RedCap UE complexity reduction |
Apple |
| R1-2311746 |
Discussion on UE complexity reduction |
DENSO CORPORATION |
| R1-2311749 |
Remaining issues on UE complexity reduction |
Sharp |
| R1-2311786 |
Remaining Issues for eRedCap |
Nokia, Nokia Shanghai Bell |
| R1-2311797 |
Remaining issues on UE complexity reduction |
Transsion Holdings |
| R1-2311848 |
Remaining issues on further UE complexity reduction for eRedCap |
Samsung |
| R1-2311894 |
Remaining issues of further UE complexity reduction for eRedCap |
LG Electronics |
| R1-2311978 |
Maintenance on eRedCap UE complexity reduction |
MediaTek Inc. |
| R1-2312040 |
UE complexity reduction for eRedCap |
Qualcomm Incorporated |
| R1-2312126 |
On maintenance of further complexity reduction of NR UE |
Nordic Semiconductor ASA |
| R1-2312167 |
Maintenance issues for Rel-18 eRedCap |
Ericsson |
| R1-2312204 |
Maintenance issues for UE Redcap |
Sony |
| R1-2312280 |
FL summary #1 on Rel-18 RedCap UE complexity reduction |
Moderator (Ericsson) |
| R1-2312281 |
FL summary #2 on Rel-18 RedCap UE complexity reduction |
Moderator (Ericsson) |
| R1-2312282 |
FL summary #3 on Rel-18 RedCap UE complexity reduction |
Moderator (Ericsson) |
| R1-2312617 |
Draft LS on eRedCap agreements on early indication in MsgA PRACH and on peak rate related capability parameters |
Ericsson |
| R1-2312618 |
LS on eRedCap agreements on early indication in MsgA PRACH and on peak rate related capability parameters |
RAN1, Ericsson |
| 8.5 |
Maintenance on Network Energy Savings for NR |
|
| R1-2312704 |
RAN1 agreements sorted per topics for Rel-18 NES |
Rapporteur (Huawei) |
| 8.5.1 |
Techniques in spatial and power domains |
|
| R1-2310863 |
Maintenance of CSI enhancements for NES |
Huawei, HiSilicon |
| R1-2310985 |
Techniques in spatial and power domains |
Nokia, Nokia Shanghai Bell |
| R1-2310993 |
Discussion on NES techniques in spatial and power domains |
ZTE, Sanechips |
| R1-2311051 |
Remaining details on NW energy saving techniques in spatial and power domains |
Fujitsu |
| R1-2311102 |
Remaining issues on NES techniques in spatial and power domain |
vivo |
| R1-2311137 |
Maintenance issues of NES spatial and power domain operations |
Intel Corporation |
| R1-2311170 |
Remaining issues on NES techniques in spatial and power domains |
Spreadtrum Communications |
| R1-2311243 |
Discussion on remaining issue for techniques in spatial and power domains |
OPPO |
| R1-2311347 |
Network Energy Saving techniques in spatial and power domain |
CATT |
| R1-2311358 |
Remaining issues on Spatial NES |
FUTUREWEI |
| R1-2311413 |
Remaining issues on NES techniques in spatial and power domains |
Beijing Xiaomi Mobile Software |
| R1-2311487 |
Remaining issues on spatial and power domains enhancements for network energy saving |
CMCC |
| R1-2311509 |
Remaining issues on network energy saving techniques in spatial and power domains |
NEC |
| R1-2311535 |
Remaining issues on NES techniques in spatial and power domains |
InterDigital, Inc. |
| R1-2311546 |
Remaining issues on CSI enhancement for NES |
China Telecom |
| R1-2311574 |
Network Energy Saving in Spatial and Power Domain |
Google |
| R1-2311656 |
Maintenance of spatial and power domain enhancements for NW energy savings |
NTT DOCOMO, INC. |
| R1-2311689 |
On remaining issues for spatial and power domain enhancements to support network energy saving |
Apple |
| R1-2311763 |
Remaining issues of spatial and power domain adaptation for network energy saving |
Panasonic |
| R1-2311798 |
Remaining issues of NES techniques in spatial and power domains |
Transsion Holdings |
| R1-2311849 |
Remaining issues on NES techniques in spatial and power domains |
Samsung |
| R1-2311895 |
Remaining issues of NES techniques in spatial and power domains |
LG Electronics |
| R1-2311933 |
Remaining issues on techniques in spatial and power domains |
Ruijie Network Co. Ltd |
| R1-2311938 |
Maintenance on Network energy saving techniques in spatial and power domains |
Lenovo |
| R1-2311980 |
Maintenance on NES techniques in spatial and power domains |
MediaTek Inc. |
| R1-2312041 |
Remaining aspects of spatial and power domain adaptation |
Qualcomm Incorporated |
| R1-2312100 |
Maintenance of NW energy saving techniques in spatial and power domains |
Ericsson |
| R1-2312113 |
Correction on spatial adaptation |
ASUSTeK |
| R1-2312159 |
Remaining issues on techniques in spatial and power domains |
CEWiT |
| R1-2312346 |
FL summary#1 for SD and PD adaptation for R18 NES |
Moderator (Huawei) |
| R1-2312347 |
FL summary#2 for SD and PD adaptation for R18 NES |
Moderator (Huawei) |
| R1-2312348 |
FL summary#3 for SD and PD adaptation for R18 NES |
Moderator (Huawei) |
| R1-2312349 |
FL summary#4 for SD and PD adaptation for R18 NES |
Moderator (Huawei) |
| R1-2312638 |
FL summary#5 for SD and PD adaptation for R18 NES |
Moderator (Huawei) |
| R1-2312639 |
Final summary for SD and PD adaptation for R18 NES |
Moderator (Huawei) |
| 8.5.2 |
Enhancements on cell DTX/DRX mechanism |
|
| R1-2310864 |
Maintenance of Cell DTX/DRX for NES |
Huawei, HiSilicon |
| R1-2310986 |
Enhancements on cell DTX/DRX mechanism |
Nokia, Nokia Shanghai Bell |
| R1-2310994 |
Discussion on cell DTX/DRX |
ZTE, Sanechips |
| R1-2311052 |
Remaining details on cell DTX DRX mechanism |
Fujitsu |
| R1-2311103 |
Remaining issues on enhancements on cell DTX/DRX mechanism |
vivo |
| R1-2311138 |
Maintenance issues of NES cell DTX/DRX operations |
Intel Corporation |
| R1-2311171 |
Remaining issues on enhancements on cell DTX/DRX mechanism |
Spreadtrum Communications |
| R1-2311244 |
Discussion on remaining issue for enhancements on cell DTX/DRX mechanism |
OPPO |
| R1-2311348 |
DTX/DRX for network Energy Saving |
CATT |
| R1-2311359 |
Remaining Issues on Cell DTX/DRX |
FUTUREWEI |
| R1-2311407 |
Discussions on cell DTX-DRX for network energy saving |
xiaomi |
| R1-2311488 |
Remaining issues on cell DTX DRX mechanism for NES |
CMCC |
| R1-2311511 |
Remaining issues on cell DTX/DRX configuration for Network Energy Saving |
NEC |
| R1-2311536 |
Remaining issues on cell DTX/DRX mechanism |
InterDigital, Inc. |
| R1-2311547 |
Remaining issues on mechanism of Cell DTX/DRX |
China Telecom |
| R1-2311575 |
Network Energy Saving on Cell DTX and DRX |
Google |
| R1-2311627 |
Maintenance on enhancements on Cell DTX/DRX mechanism |
NTT DOCOMO, INC. |
| R1-2311690 |
On remaining issues for cell DTX/DRX mechanism |
Apple |
| R1-2311754 |
Remaining issues on cell DTX/DRX mechanism |
ETRI |
| R1-2311764 |
Remaining issues of Cell DTX/DRX enhancement for network energy saving |
Panasonic |
| R1-2311799 |
Remaining issues on enhancement on cell DTXDRX mechanism |
Transsion Holdings |
| R1-2311850 |
Remaining issues on cell DTX/DRX mechanism |
Samsung |
| R1-2311896 |
Remaining issues of cell DTX/DRX mechanism |
LG Electronics |
| R1-2311939 |
Maintenance on enhancements on cell DTX/DRX mechanism |
Lenovo |
| R1-2311981 |
Maintenance on cell DTX/DRX mechanism |
MediaTek Inc. |
| R1-2312042 |
Remaining aspects of cell DTX and DRX |
Qualcomm Incorporated |
| R1-2312101 |
Maintenance for cell DTX/DRX |
Ericsson |
| R1-2312112 |
Correction on cell DTX DRX |
ASUSTeK |
| R1-2312161 |
Discussion on cell DTX/DRX mechanism |
CEWiT |
| R1-2312313 |
Summary of maintenance issues for enhancements on cell DTX/DRX mechanism |
Moderator (Intel Corporation) |
| R1-2312314 |
Discussion summary #1 for enhancements on cell DTX/DRX mechanism |
Moderator (Intel Corporation) |
| R1-2312315 |
Discussion summary #2 for enhancements on cell DTX/DRX mechanism |
Moderator (Intel Corporation) |
| R1-2312409 |
LS on Cell DTX/DRX operations for sTRP |
RAN1, Intel Corporation |
| R1-2312410 |
Discussion summary #3 for enhancements on cell DTX/DRX mechanism |
Moderator (Intel Corporation) |
| R1-2312411 |
Discussion summary #4 for enhancements on cell DTX/DRX mechanism |
Moderator (Intel Corporation) |
| R1-2312412 |
Discussion summary #5 for enhancements on cell DTX/DRX mechanism |
Moderator (Intel Corporation) |
| R1-2312606 |
Discussion summary #6 for enhancements on cell DTX/DRX mechanism |
Moderator (Intel Corporation) |
| R1-2312607 |
Discussion summary #7 for enhancements on cell DTX/DRX mechanism |
Moderator (Intel Corporation) |
| 8.6.1 |
XR-specific capacity enhancements |
|
| R1-2310832 |
Remaining issues of XR-specific capacity enhancements |
FUTUREWEI |
| R1-2310995 |
Discussion on remaining issues of XR |
ZTE, Sanechips |
| R1-2311104 |
Remaining issue on XR specific capacity enhancements |
vivo |
| R1-2311273 |
Remaining issues on XR specific capacity enhancements |
OPPO |
| R1-2311349 |
Design of Multiple CG Occasions and unused CG occasion feedback |
CATT |
| R1-2311408 |
Remaining issues on XR-specific capacity enhancements |
xiaomi |
| R1-2311489 |
Remaining issues on XR-specific capacity enhancements |
CMCC |
| R1-2311533 |
Remaining issues on XR-specific capacity enhancements |
InterDigital, Inc. |
| R1-2311628 |
Discussion on maintenance on XR enhancements |
NTT DOCOMO, INC. |
| R1-2311691 |
Remaining issues in XR-specific capacity enhancements |
Apple |
| R1-2311732 |
XR-specific capacity enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2311851 |
Remaining issues on XR |
Samsung |
| R1-2311897 |
Remaining issues on XR-specific capacity enhancements |
LG Electronics |
| R1-2311905 |
On Maintenance of XR enhancements for NR |
Ericsson |
| R1-2311953 |
Clarification on UTO-UCI and HARQ-ACK multiplexing on PUSCH |
Sharp |
| R1-2312043 |
Maintenance on XR Enhancements |
Qualcomm Incorporated |
| R1-2312217 |
Maintenance of CG enhancements for XR capacity |
Huawei, HiSilicon |
| R1-2312385 |
Moderator Summary#1 - Maintenance of XR Enhancements |
Moderator (Ericsson) |
| R1-2312386 |
Moderator Summary#2 - Maintenance of XR Enhancements |
Moderator (Ericsson) |
| R1-2312387 |
Moderator Summary#3 - Maintenance of XR Enhancements |
Moderator (Ericsson) |
| 8.7 |
Maintenance on Further NR Mobility Enhancements |
|
| R1-2312391 |
Summary of RRC parameters for NR mobility enhancement WI for RAN1 115 meeting |
Rapporteur (Apple) |
| R1-2312469 |
RRC parameters list update #1 for NR mobility enhancement WI |
Rapporteur (Apple) |
| R1-2312506 |
Session notes for 8.7 (Maintenance on further NR mobility enhancements) |
Ad-Hoc Chair (Huawei) |
| R1-2312542 |
Summary#2 of RRC parameters for NR mobility enhancement WI |
Rapporteur (Apple) |
| R1-2312616 |
Summary#3 of RRC parameters for NR mobility enhancement WI |
Rapporteur (Apple) |
| R1-2312679 |
Summary#4 of RRC parameters for NR mobility enhancement WI |
Rapporteur (Apple) |
| R1-2312680 |
RRC parameters list update #2 for NR mobility enhancement WI |
Rapporteur (Apple) |
| 8.7.1 |
L1 enhancements for inter-cell beam management |
|
| R1-2310830 |
Remaining issues of L1 enhancements for inter-cell beam management |
FUTUREWEI |
| R1-2310848 |
Maintenance of L1 enhancements for inter-cell beam management |
Huawei, HiSilicon |
| R1-2310954 |
Maintenance on L1 enhancements for inter-cell beam management |
ZTE |
| R1-2310972 |
Maintenance of L1 enhancements to inter-cell beam management |
Ericsson |
| R1-2311034 |
FL plan on L1 enhancements for LTM at RAN1#115 |
Moderator (Fujitsu) |
| R1-2311035 |
FL summary 1 on L1 enhancements for inter-cell beam management |
Moderator (Fujitsu) |
| R1-2311036 |
FL summary 2 on L1 enhancements for inter-cell beam management |
Moderator (Fujitsu) |
| R1-2311037 |
FL summary 3 on L1 enhancements for inter-cell beam management |
Moderator (Fujitsu) |
| R1-2311038 |
Final FL summary on L1 enhancements for inter-cell beam management |
Moderator (Fujitsu) |
| R1-2311053 |
Remaining issues on L1 enhancements for inter-cell beam management |
Fujitsu |
| R1-2311105 |
Discussion on L1 enhancement for L1/L2-triggered Mobility |
vivo |
| R1-2311172 |
Remaining issues on L1 enhancements for inter-cell beam management |
Spreadtrum Communications |
| R1-2311212 |
Remaining issues on L1 enhancement for LTM |
Panasonic |
| R1-2311230 |
Remaining Issues of Inter-cell beam management enhancement |
OPPO |
| R1-2311350 |
Remaining issues on L1 enhancements for inter-cell beam management |
CATT |
| R1-2311368 |
Remaining issues of L1 enhancements for inter-cell beam management |
Lenovo |
| R1-2311409 |
Maintenance of L1 enhancements for inter-cell beam management |
xiaomi |
| R1-2311442 |
Maintenance on L1 enhancements for inter-cell beam management |
Google |
| R1-2311490 |
Remaining issues on L1 enhancements for inter-cell beam management |
CMCC |
| R1-2311510 |
Remaining issues on L1 enhancements for inter-cell beam management |
NEC |
| R1-2311514 |
Remaining issues on L1 enhancements for L1/L2-triggered Mobility |
KDDI Corporation |
| R1-2311593 |
Discussion on L1 enhancements for inter-cell beam management |
FGI |
| R1-2311629 |
Remaining issues on L1 enhancements for inter-cell mobility |
NTT DOCOMO, INC. |
| R1-2311692 |
L1 enhancements for inter-cell beam management |
Apple |
| R1-2311852 |
Remaining details on L1 enhancements for inter-cell beam management |
Samsung |
| R1-2311889 |
Remaining Issues on Layer-1 Enhancements for L1/L2-triggered Mobility |
Nokia, Nokia Shanghai Bell |
| R1-2311934 |
Remaining issues on L1 enhancements for inter-cell beam management |
Ruijie Network Co. Ltd |
| R1-2311951 |
Remaining issues on L1 enhancements |
InterDigital, Inc. |
| R1-2311984 |
Remaining issues on L1 enhancements for inter-cell beam management |
MediaTek Inc. |
| R1-2312044 |
L1 Enhancements for Inter-Cell Beam Management |
Qualcomm Incorporated |
| R1-2312275 |
Maintenance of L1 enhancements to inter-cell beam management |
Ericsson |
| R1-2312442 |
Draft reply LS on L1 measurements in LTM |
Moderator (Ericsson) |
| R1-2312443 |
Reply LS on L1 measurements in LTM |
RAN1, Ericsson |
| R1-2312546 |
[draft] LS on MAC CE to activate/deactivate semi-persistent PUCCH report and activation/deactivation of activated TCI states of multiple candidate cells for LTM |
Moderator (Fujitsu) |
| R1-2312547 |
[draft] LS on MAC CE to activate/deactivate semi-persistent PUCCH report for LTM |
Moderator (Fujitsu) |
| R1-2312642 |
LS on MAC CE to activate/deactivate semi-persistent PUCCH report for LTM |
RAN1, Fujitsu |
| R1-2312678 |
Final FL summary on L1 enhancements for inter-cell beam management |
Moderator (Fujitsu) |
| 8.7.2 |
Timing advance management to reduce latency |
|
| R1-2310831 |
Remaining issues with UE based TA determination |
FUTUREWEI |
| R1-2310849 |
Maintenance of timing advance management to reduce latency |
Huawei, HiSilicon |
| R1-2310955 |
Maintenance on TA management to reduce latency |
ZTE |
| R1-2310973 |
Maintenance of TA management for LTM |
Ericsson |
| R1-2311106 |
Discussion on TA management for L1/L2-triggered Mobility |
vivo |
| R1-2311173 |
Remaining issues on timing advance management to reduce latency |
Spreadtrum Communications |
| R1-2311231 |
Remaining Issues of Timing Advance Management |
OPPO |
| R1-2311351 |
Remaining issues on TA management to reduce latency |
CATT |
| R1-2311369 |
Remaining issues of timing advance management for L1/L2 mobility |
Lenovo |
| R1-2311439 |
Remaining issues on TA management for mobility |
LG Electronics |
| R1-2311443 |
Maintenance on timing advance management to reduce latency |
Google |
| R1-2311491 |
Remaining issues on timing advance management to reduce latency |
CMCC |
| R1-2311592 |
Remaining issues on TA management for LTM |
FGI |
| R1-2311630 |
Remaining issues on TA enhancements for inter-cell mobility |
NTT DOCOMO, INC. |
| R1-2311693 |
Timing advance management for L1/L2 Mobility |
Apple |
| R1-2311853 |
Remaining issues on candidate cell TA management for NR L1/L2 mobility enhancement |
Samsung |
| R1-2311890 |
Remaining Issues on Timing Advance Management for L1/L2-triggered Mobility |
Nokia, Nokia Shanghai Bell |
| R1-2311952 |
Remaining details on timing advance management |
InterDigital, Inc. |
| R1-2312045 |
TA management to reduce latency for L1/L2 based mobility |
Qualcomm Incorporated |
| R1-2312134 |
Discussion on TA management to reduce latency |
CAICT |
| R1-2312331 |
Moderator summary on timing advance management for LTM: Round 1 |
Moderator (CATT) |
| R1-2312332 |
Moderator summary on timing advance management for LTM: Round 2 |
Moderator (CATT) |
| R1-2312564 |
Moderator summary on timing advance management for LTM: Round 3 |
Moderator (CATT) |
| R1-2312565 |
Moderator summary on timing advance management for LTM: Round 4 |
Moderator (CATT) |
| 8.8 |
Maintenance on Further NR Coverage Enhancements |
|
| R1-2312507 |
Session notes for 8.8 (Maintenance on further NR coverage enhancements) |
Ad-Hoc Chair (Huawei) |
| 8.8.1 |
PRACH coverage enhancements |
|
| R1-2310882 |
Maintenance of PRACH coverage enhancements |
Huawei, HiSilicon |
| R1-2310930 |
Discussions on the remaining issue on PRACH coverage enhancements |
New H3C Technologies Co., Ltd. |
| R1-2311019 |
Maintenance of PRACH coverage enhancements |
ZTE |
| R1-2311054 |
Remaining issues on PRACH coverage enhancements |
Fujitsu |
| R1-2311107 |
Discussions on remaining issues of PRACH coverage enhancements |
vivo |
| R1-2311134 |
Remaining issues on PRACH coverage enhancement |
Intel Corporation |
| R1-2311174 |
Remaining issues on PRACH coverage enhancements |
Spreadtrum Communications |
| R1-2311263 |
Remaining issues on PRACH coverage enhancements |
OPPO |
| R1-2311352 |
Remaining issues on PRACH coverage enhancements |
CATT |
| R1-2311410 |
Discussion on PRACH coverage enhancements |
xiaomi |
| R1-2311426 |
Maintenance on PRACH coverage enhancement |
NEC |
| R1-2311444 |
Discussion on PRACH coverage enhancements |
Panasonic |
| R1-2311492 |
Remaining issues on PRACH coverage enhancements |
CMCC |
| R1-2311526 |
Remaining issues on multiple PRACH transmissions for PRACH coverage enhancement |
Sony |
| R1-2311548 |
Remaining issues on PRACH coverage enhancement |
China Telecom |
| R1-2311631 |
Remaining issues on PRACH coverage enhancements |
NTT DOCOMO, INC. |
| R1-2311694 |
Remaining issues on PRACH coverage enhancements |
Apple |
| R1-2311717 |
Remaining issues on PRACH coverage enhancements |
Quectel |
| R1-2311723 |
Remaining issues on PRACH coverage enhancements |
Lenovo |
| R1-2311755 |
PRACH coverage enhancements |
ETRI |
| R1-2311770 |
Remaining issues on multiple PRACH transmissions for Rel-18 CovEnh |
Sharp |
| R1-2311854 |
PRACH coverage enhancements |
Samsung |
| R1-2311915 |
Remaining issues on PRACH coverage enhancements |
LG Electronics |
| R1-2311920 |
Remaining issues on PRACH coverage enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2311935 |
Maintenance on PRACH coverage enhancements |
Ruijie Network Co. Ltd |
| R1-2311945 |
Discussion on PRACH Coverage Enhancement |
Ericsson |
| R1-2311986 |
Maintenance for PRACH coverage enhancements |
MediaTek Inc. |
| R1-2312132 |
Remaining issues on PRACH coverage enhancements |
Google Inc. |
| R1-2312272 |
FL Summary #1 on remaining issues for PRACH coverage enhancements |
Moderator (China Telecom) |
| R1-2312273 |
FL Summary #2 on remaining issues for PRACH coverage enhancements |
Moderator (China Telecom) |
| R1-2312274 |
FL Summary #3 on remaining issues for PRACH coverage enhancements |
Moderator (China Telecom) |
| R1-2312633 |
FL Summary #4 on remaining issues for PRACH coverage enhancements |
Moderator (China Telecom) |
| R1-2312677 |
FL Summary #5 on remaining issues for PRACH coverage enhancements |
Moderator (China Telecom) |
| 8.8.2 |
Power domain enhancements |
|
| R1-2310883 |
Discussion on coverage enhancement in power domain |
Huawei, HiSilicon |
| R1-2311020 |
Maintenance of power domain enhancements |
ZTE |
| R1-2311108 |
Discussions on remaining issues of power domain enhancements |
vivo |
| R1-2311175 |
Remaining issues on power domain enhancement |
Spreadtrum Communications |
| R1-2311264 |
Remaining issues on of power domain enhancements |
OPPO |
| R1-2311353 |
Remaining issue on power domain enhancements |
CATT |
| R1-2311411 |
Maintenance on power domain enhancements |
xiaomi |
| R1-2311493 |
Remaining issues on power domain enhancements |
CMCC |
| R1-2311549 |
Remaining issues on Power domain enhancements |
China Telecom |
| R1-2311724 |
Remaining issues on dynamic switching between DFT-S-OFDM and CP-OFDM |
Lenono |
| R1-2311855 |
Power domain enhancements |
Samsung |
| R1-2311921 |
Remaining issues on power domain enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2311946 |
Power Domain Enhancement Maintenance |
Ericsson |
| R1-2312046 |
Power-domain enhancements |
Qualcomm Incorporated |
| R1-2312304 |
FL summary of power domain enhancements (AI 8.8.2) |
Moderator (Nokia) |
| R1-2312305 |
FL summary #2 of power domain enhancements (AI 8.8.2) |
Moderator (Nokia) |
| R1-2312306 |
Final FL summary of power domain enhancements (AI 8.8.2) |
Moderator (Nokia) |
| 8.8.3 |
Dynamic switching between DFT-S-OFDM and CP-OFDM |
|
| R1-2310884 |
Maintenance of dynamic waveform switching for coverage enhancement |
Huawei, HiSilicon |
| R1-2311021 |
Maintenance of dynamic waveform switching |
ZTE |
| R1-2311109 |
Discussions on remaining issues of dynamic waveform switching |
vivo |
| R1-2311135 |
Remaining issues on dynamic waveform switching |
Intel Corporation |
| R1-2311265 |
Issues on dynamic switching between DFT-S-OFDM and CP-OFDM |
OPPO |
| R1-2311354 |
Remaining issue on dynamic waveform switching |
CATT |
| R1-2311412 |
Maintenance on dynamic switching between DFT-s-OFDM and CP-OFDM |
xiaomi |
| R1-2311427 |
Maintenance on dynamic switching between DFT-S-OFDM and CP-OFDM |
NEC |
| R1-2311445 |
Discussion on the remaining issues for dynamic waveform switching |
Panasonic |
| R1-2311494 |
Remaining issues on dynamic switching between DFT-S-OFDM and CP-OFDM |
CMCC |
| R1-2311532 |
Dynamic switching between DFT-S-OFDM and CP-OFDM |
InterDigital, Inc. |
| R1-2311550 |
Remaining issues on DWS between CP-OFDM and DFT-s-OFDM |
China Telecom |
| R1-2311632 |
Remaining issues on dynamic switching between DFT-S-OFDM and CP-OFDM |
NTT DOCOMO, INC. |
| R1-2311695 |
Remaining issues on dynamic switching between DFT-S-OFDM and CP-OFDM |
Apple |
| R1-2311756 |
Dynamic switching between DFT-S-OFDM and CP-OFDM |
ETRI |
| R1-2311771 |
Remaining issues on dynamic waveform switching for Rel-18 CovEnh |
Sharp |
| R1-2311856 |
Dynamic switching between DFT-S-OFDM and CP-OFDM |
Samsung |
| R1-2311916 |
Remaining issues on dynamic waveform switching for NR coverage enhancement |
LG Electronics |
| R1-2311922 |
Remaining issues on dynamic switching between DFT-s-OFDM and CP-OFDM |
Nokia, Nokia Shanghai Bell |
| R1-2311947 |
Discussion on Dynamic UL Waveform Switching |
Ericsson |
| R1-2312047 |
Dynamic switching between DFT-S-OFDM and CP-OFDM |
Qualcomm Incorporated |
| R1-2312109 |
Summary #1 on dynamic switching between DFT-S-OFDM and CP-OFDM |
Moderator (InterDigital, Inc.) |
| R1-2312111 |
Summary #2 on dynamic switching between DFT-S-OFDM and CP-OFDM |
Moderator (InterDigital, Inc.) |
| R1-2312158 |
Maintenance issues on DWS Configuration |
Sony |
| R1-2312205 |
Remaining issues on dynamic switching between DFT-S-OFDM and CP-OFDM |
Google Inc. |
| R1-2312338 |
Draft reply LS on PHR reporting |
Moderator (InterDigital, Inc.) |
| R1-2312339 |
Reply LS on PHR reporting |
RAN1, InterDigital, Inc. |
| R1-2312622 |
Summary #3 on dynamic switching between DFT-S-OFDM and CP-OFDM |
Moderator (InterDigital, Inc.) |
| R1-2312623 |
Summary #4 on dynamic switching between DFT-S-OFDM and CP-OFDM |
Moderator (InterDigital, Inc.) |
| 8.9 |
Maintenance on NR Support for Dedicated Spectrum Less than 5MHz for FR1 |
|
| R1-2311357 |
Introduction of NR support for dedicated spectrum less than 5MHz for FR1 to TS 38.300 |
Nokia (WI Rapporteur) |
| R1-2312457 |
DRAFT LS on Introduction of NR support for dedicated spectrum less than 5MHz for FR1 to TS 38.300 |
Moderator (Nokia) |
| R1-2312458 |
LS on Introduction of NR support for dedicated spectrum less than 5MHz for FR1 to TS 38.300 |
RAN1, Nokia |
| R1-2312508 |
Session notes for 8.9 (Maintenance on NR support for dedicated spectrum less than 5MHz for FR1) |
Ad-Hoc Chair (Huawei) |
| 8.9.1 |
Enhancements to operate NR on dedicated spectrum less than 5 MHz |
|
| R1-2310966 |
Maintenance on NR support of spectrum less than 5MHz for FR1 |
Ericsson |
| R1-2311022 |
Remaining issues on dedicated spectrum less than 5 MHz |
ZTE |
| R1-2311355 |
Discussion on enhancements to operate NR on dedicated spectrum less than 5MHz |
CATT |
| R1-2311356 |
NR support for below 5 MHz BW |
Nokia, Nokia Shanghai Bell |
| R1-2311633 |
Remaining issues on enhancements to operate NR on dedicated spectrum less than 5 MHz |
NTT DOCOMO, INC. |
| R1-2311725 |
Remaining issues on dedicated spectrum less than 5 MHz |
Lenovo |
| R1-2311857 |
Maintenance on enhancements to operate NR on dedicated spectrum less than 5 MHz |
Samsung |
| R1-2311898 |
Remaining issues of enhancements for dedicated spectrum less than 5 MHz |
LG Electronics |
| R1-2311988 |
Maintenance on dedicated spectrum less than 5MHz |
MediaTek Inc. |
| R1-2312048 |
NR support for dedicated spectrum less than 5MHz for FR1 |
Qualcomm Incorporated |
| R1-2312133 |
Further discussion on dedicated spectrum less than 5MHz for FR1 |
TD Tech, Chengdu TD Tech |
| R1-2312151 |
Enhancements to operate NR on dedicated spectrum less than 5 MHz |
Huawei, HiSilicon |
| R1-2312397 |
Summary#1 of discussion on enhancements to operate NR on dedicated spectrum less than 5MHz |
Moderator (Lenovo) |
| R1-2312398 |
Summary#2 of discussion on enhancements to operate NR on dedicated spectrum less than 5MHz |
Moderator (Lenovo) |
| R1-2312563 |
DRAFT LS on inter-frequency neighbour cells supporting NR dedicated spectrum less than 5 MHz for FR1 |
Qualcomm Incorporated |
| R1-2312567 |
Summary#3 of discussion on enhancements to operate NR on dedicated spectrum less than 5MHz |
Moderator (Lenovo) |
| R1-2312602 |
DRAFT LS on inter-frequency neighbour cells supporting NR dedicated spectrum less than 5 MHz for FR1 |
Qualcomm Incorporated |
| R1-2312668 |
LS on inter-frequency neighbour cells supporting NR dedicated spectrum less than 5 MHz for FR1 |
RAN1, Qualcomm Incorporated |
| 8.10 |
Maintenance on Enhancement of NR Dynamic Spectrum Sharing (DSS) |
|
| R1-2312509 |
Session notes for 8.10 (Maintenance on enhancement of NR Dynamic Spectrum Sharing) |
Ad-Hoc Chair (Huawei) |
| 8.10.1 |
NR PDCCH reception in symbols with LTE CRS Res |
|
| R1-2311023 |
Maintenance of NR PDCCH reception in symbols with LTE CRS |
ZTE |
| R1-2311274 |
Remaining issues for PDCCH reception in overlapping with LTE CRS |
OPPO |
| R1-2311450 |
Monitoring of PDCCH candidates overlapping with LTE CRS |
Nokia, Nokia Shanghai Bell |
| R1-2311696 |
Maintenance of NR PDCCH reception in symbols with LTE CRS |
Apple |
| R1-2312219 |
Maintenance of NR PDCCH reception in symbols with LTE CRS REs |
Huawei, HiSilicon |
| R1-2312367 |
Moderator Summary#1 for Rel. 18 eDSS |
Moderator (Intel Corporation) |
| R1-2312368 |
Moderator Summary#2 for Rel. 18 eDSS |
Moderator (Intel Corporation) |
| 8.11 |
Maintenance on NR Network-Controlled Repeaters |
|
| R1-2312671 |
List of agreements on NCR in RAN1#115 |
ZTE |
| 8.11.1 |
Side control information and NCR behaviour |
|
| R1-2310860 |
Maintenance of side control information and NCR behaviour |
Huawei, HiSilicon |
| R1-2311030 |
Side-control information and NCR behaviour |
Ericsson |
| R1-2311045 |
Remaining issues on side control information and NCR behaviour |
Fujitsu |
| R1-2311128 |
Discussion on side control information and NCR behavior |
Nokia, Nokia Shanghai Bell |
| R1-2311176 |
Remaining issue on side control information and NCR behavior |
Spreadtrum Communications |
| R1-2311197 |
Remaining issue on side control information and NCR behavior |
ZTE |
| R1-2311282 |
Maintenance on side control information and NCR behavior |
Panasonic |
| R1-2311321 |
Maintenance on side control information and NCR behaviour for NR Network-Controlled Repeaters |
CATT |
| R1-2311386 |
Discussion on remaining issues of NCR |
xiaomi |
| R1-2311495 |
Remaining issues on side control information and NCR behaviour |
CMCC |
| R1-2311551 |
Remaining issues on side control information and NCR behaviour |
China Telecom |
| R1-2311697 |
On remaining issues for side control information for NCR |
Apple |
| R1-2311757 |
Discussion on NCR maintenance |
ETRI |
| R1-2311858 |
Remaining Issues on side control information and NCR behaviour |
Samsung |
| R1-2311917 |
Remaining issues on side control information and NCR behaviour |
LG Electronics |
| R1-2312375 |
Summary#1 of maintenance issues on side control information and NCR behavior |
Moderator (ZTE) |
| R1-2312535 |
Summary#2 of maintenance issues on side control information and NCR behavior |
Moderator (ZTE) |
| 8.11.2 |
Other aspects including control plane signalling and procedures relevant to RAN1 |
|
| R1-2310861 |
Maintenance of other aspects for NCR |
Huawei, HiSilicon |
| R1-2311031 |
Control-plane signaling and procedures for NCR |
Ericsson |
| R1-2311129 |
Discussion on other aspects including control plane signalling and procedures relevant to RAN1 |
Nokia, Nokia Shanghai Bell |
| R1-2311198 |
Remaining issue on other aspects of NCR |
ZTE |
| R1-2311322 |
Maintenance on other aspects including control plane signalling and procedures relevant to RAN1 for NR Network-Controlled Repeaters |
CATT |
| R1-2311859 |
Remaining Issues on signaling and procedures for network-controlled repeaters |
Samsung |
| R1-2312307 |
Summary#1 on other aspects |
Moderator (Fujitsu) |
| 8.12 |
Maintenance on Multi-Carrier Enhancements for NR |
|
| R1-2312541 |
Summary of discussion on higher layer parameters list for MCE |
Moderator (NTT DOCOMO, INC.) |
| 8.12.1 |
Multi-cell PUSCH/PDSCH scheduling with a single DCI |
|
| R1-2310887 |
Maintenance of multi-cell PDSCCH/PUSCH scheduling with a single DCI |
Huawei, HiSilicon |
| R1-2311024 |
Maintenance of Multi-cell PUSCH/PDSCH scheduling with a single DCI |
ZTE |
| R1-2311046 |
Remaining issues on multi-cell PUSCH/PDSCH scheduling with a single DCI |
Fujitsu |
| R1-2311110 |
Remaining issues on Rel-18 Multi-cell scheduling |
vivo |
| R1-2311177 |
Remaining issues on multi-cell PUSCH/PDSCH scheduling with a single DCI |
Spreadtrum Communications |
| R1-2311275 |
Remaining issues for multi-cell PUSCH/PDSCH scheduling with a single DCI |
OPPO |
| R1-2311323 |
Maintenance on Multi-cell PUSCH/PDSCH scheduling with a single DCI |
CATT |
| R1-2311387 |
Remaining issues on multi-cell PUSCH/PDSCH scheduling with a single DCI |
xiaomi |
| R1-2311496 |
Remaining issues on multi-cell PUSCH/PDSCH scheduling with a single DCI |
CMCC |
| R1-2311520 |
On Rel-18 MC-DCI scheduling |
Nokia, Nokia Shanghai Bell |
| R1-2311552 |
Remaining issues on multi-cell scheduling with a single DCI |
China Telecom |
| R1-2311587 |
Remaining issues on Rel-18 multi-carrier enhancements |
Lenovo |
| R1-2311634 |
Maintenance on multi-cell PUSCH/PDSCH scheduling with a single DCI |
NTT DOCOMO, INC. |
| R1-2311698 |
On remaining issues for Rel-18 multi-cell scheduling |
Apple |
| R1-2311735 |
Remaining issues on multi-cell PUSCH/PDSCH scheduling with a single DCI |
Langbo |
| R1-2311758 |
Remaining issues on multi-cell PUSCH/PDSCH scheduling |
ETRI |
| R1-2311860 |
Remaining issues on multi-cell PUSCH/PDSCH scheduling with a single DCI |
Samsung |
| R1-2311899 |
Remaining issues on Multi-cell scheduling with single DCI |
LG Electronics |
| R1-2311990 |
On maintenance for multi-cell scheduling with a single DCI |
MediaTek Inc. |
| R1-2312049 |
Multi-cell PUSCH/PDSCH scheduling with a single DCI |
Qualcomm Incorporated |
| R1-2312102 |
Maintenance for single DCI scheduling multiple cells |
Ericsson |
| R1-2312115 |
Remaining detail on multi-cell scheduling PUSCH/PDSCH with a single DCI |
ITRI |
| R1-2312360 |
Feature lead summary#1 on multi-cell PUSCH/PDSCH scheduling with a single DCI |
Moderator (Lenovo) |
| R1-2312361 |
Feature lead summary#2 on multi-cell PUSCH/PDSCH scheduling with a single DCI |
Moderator (Lenovo) |
| R1-2312362 |
Feature lead summary#3 on multi-cell PUSCH/PDSCH scheduling with a single DCI |
Moderator (Lenovo) |
| R1-2312513 |
Feature lead summary#4 on multi-cell PUSCH/PDSCH scheduling with a single DCI |
Moderator (Lenovo) |
| R1-2312514 |
Feature lead summary#5 on multi-cell PUSCH/PDSCH scheduling with a single DCI |
Moderator (Lenovo) |
| 8.12.2 |
Multi-carrier UL Tx switching scheme |
|
| R1-2310888 |
Maintenance of multi-carrier UL Tx switching schemes |
Huawei, HiSilicon |
| R1-2311025 |
Maintenance of Multi-carrier UL Tx switching scheme |
ZTE |
| R1-2311111 |
Remaining issues on Rel-18 UL Tx switching across 3 or 4 bands |
vivo |
| R1-2311178 |
Remaining issues on UL Tx switching |
Spreadtrum Communications |
| R1-2311276 |
Remaining issues on multi-carrier UL Tx switching scheme |
OPPO |
| R1-2311324 |
Maintenance on Multi-carrier UL Tx switching scheme |
CATT |
| R1-2311388 |
Remaining issues on multi-carrier UL Tx switching scheme |
xiaomi |
| R1-2311466 |
On remaining issues of Multi-carrier UL Tx switching CR to 38.214 |
Nokia, Nokia Shanghai Bell |
| R1-2311497 |
Remaining issues on multi-carrier UL Tx switching scheme |
CMCC |
| R1-2311553 |
Remaining issues on Rel-18 UL Tx switching |
China Telecom |
| R1-2311635 |
Maintenance on multi-carrier UL Tx switching scheme |
NTT DOCOMO, INC. |
| R1-2311699 |
On remaining issues for Rel-18 UL Tx switching |
Apple |
| R1-2311900 |
Remaining issues on Multi-carrier UL Tx switching scheme |
LG Electronics |
| R1-2311907 |
On Maintenance for Multi-Carrier UL TX switching |
Ericsson |
| R1-2312050 |
Discussion on Rel-18 UL Tx switching |
Qualcomm Incorporated |
| R1-2312284 |
Summary of discussion on Multi-carrier UL Tx switching scheme |
Moderator (NTT DOCOMO, INC.) |
| R1-2312426 |
Summary#2 of discussion on Multi-carrier UL Tx switching scheme |
Moderator (NTT DOCOMO, INC.) |
| R1-2312517 |
Summary#3 of discussion on Multi-carrier UL Tx switching scheme |
Moderator (NTT DOCOMO, INC.) |
| R1-2312663 |
Summary#4 of discussion on Multi-carrier UL Tx switching scheme |
Moderator (NTT DOCOMO, INC.) |
| R1-2312664 |
Summary#5 of discussion on Multi-carrier UL Tx switching scheme |
Moderator (NTT DOCOMO, INC.) |
| R1-2312694 |
Summary#6 of discussion on Multi-carrier UL Tx switching scheme |
Moderator (NTT DOCOMO, INC.) |
| R1-2312695 |
Summary#7 of discussion on Multi-carrier UL Tx switching scheme |
Moderator (NTT DOCOMO, INC.) |
| 8.13 |
Maintenance on NTN (Non-Terrestrial Networks) Enhancements |
|
| R1-2310877 |
Discussion on RAN1 impact to support the RAN4 work on NTN above 10GHz |
Huawei, HiSilicon |
| R1-2310917 |
On RAN1 impact of NTN above 10 GHz |
Ericsson |
| R1-2310936 |
Considerations on the system parameters for FR2-NTN |
THALES |
| R1-2311199 |
Discussion on the RAN1 related aspects for NTN above 10 GHz |
ZTE |
| R1-2311312 |
Remaining issue on NTN above 10 GHz |
CATT |
| R1-2311429 |
Power control for RACH-less handover in NR NTN |
NEC |
| R1-2311585 |
Discussion on the RAN1 impact for NTN above 10GHz |
Beijing Xiaomi Mobile Software |
| R1-2311636 |
Discussion on FR2-NTN for NR NTN |
NTT DOCOMO, INC. |
| R1-2311700 |
Discussion on NTN above 10 GHz |
Apple |
| R1-2311772 |
Discussions on RAN4 LS on FR2-NTN aspects |
Sharp |
| R1-2311996 |
Discussion on RAN4 LS on the system parameters for NTN above 10 GHz |
MediaTek Inc. |
| R1-2312051 |
On RACH-less handover in NR NTN |
Qualcomm Incorporated |
| R1-2312136 |
Further discussion of open issues related to NTN operation in frequency bands above 10 GHz |
Nokia, Nokia Shanghai Bell |
| R1-2312141 |
Summary #1 for FR2-NTN |
Moderator (Nokia) |
| R1-2312142 |
Summary #2 for FR2-NTN |
Moderator (Nokia) |
| R1-2312246 |
TP for TS 38.300 |
THALES |
| R1-2312247 |
On RAN1 related aspects for NTN above 10 GHz |
Mitsubishi Electric RCE |
| R1-2312301 |
Rel-18 Higher Layer Parameters for IoT NTN |
Moderator (MediaTek) |
| R1-2312377 |
Summary of discussion on remaining issues for RACH-less handover |
Moderator (Samsung) |
| R1-2312424 |
Rel-18 Higher Layer Parameters for NR NTN |
Moderator (THALES) |
| R1-2312495 |
TP for TS 38.300 |
Moderator (THALES) |
| R1-2312496 |
LS on NR-NTN TP for TS 38.300 |
RAN1, THALES |
| R1-2312510 |
Session notes for 8.13 (Maintenance on NTN (Non-Terrestrial Networks) enhancements) |
Ad-Hoc Chair (Huawei) |
| R1-2312518 |
FLS#1 on NR-NTN TP for TS 38.300 |
Moderator (THALES) |
| R1-2312553 |
Response on LS on the system parameters for NTN above 10 GHz |
RAN1, Nokia |
| R1-2312625 |
FLS#2 on NR-NTN TP for TS 38.300 |
Moderator (THALES) |
| R1-2312655 |
RAN1 agreements for Rel-18 WI on IoT NTN enhancements up to RAN1#115 |
Moderator (MediaTek Inc.) |
| R1-2312669 |
TP for TS 38.300 |
Moderator (THALES) |
| R1-2312670 |
LS on NR-NTN TP for TS 38.300 |
RAN1, THALES |
| R1-2312681 |
LS on NR-NTN TP for TS 38.300 |
RAN1, THALES |
| 8.13.1 |
Coverage enhancement for NR NTN |
|
| R1-2310874 |
Maintenance of coverage enhancement for NR NTN |
Huawei, HiSilicon |
| R1-2310916 |
On maintenance of coverage enhancements for NR NTN |
Ericsson |
| R1-2311112 |
Discussions on remaining issues of coverage enhancements in NR NTN |
vivo |
| R1-2311179 |
Remaining issues on coverage enhancements for NTN |
Spreadtrum Communications |
| R1-2311200 |
Remaining issue on coverage enhancement |
ZTE |
| R1-2311245 |
Discussion on remaining issue for coverage enhancement for NR NTN |
OPPO |
| R1-2311389 |
Discussion on remaining issues on coverage enhancement for NR-NTN |
xiaomi |
| R1-2311498 |
Remaining issues on coverage enhancement for NR NTN |
CMCC |
| R1-2311513 |
Remaining issues on NR NTN Coverage Enhancement |
NEC |
| R1-2311637 |
Maintenance on coverage enhancement for NR NTN |
NTT DOCOMO, INC. |
| R1-2311773 |
Maintenance on coverage enhancement for NR NTN |
Sharp |
| R1-2311861 |
Remaining issues on coverage enhancement for NR NTN |
Samsung |
| R1-2311918 |
Remaining issues of coverage enhancement for NR NTN |
LG Electronics |
| R1-2311994 |
Coverage enhancement for NR NTN |
MediaTek Inc. |
| R1-2312004 |
Remaining issues on coverage enhancements for NR NTN |
Hyundai Motor Company |
| R1-2312052 |
Maintenance on coverage enhancements for NR NTN |
Qualcomm Incorporated |
| R1-2312091 |
Maintenance of coverage enhancement for NR NTN |
Baicells |
| R1-2312137 |
Open issues related to coverage enhancements for NR over NTN |
Nokia, Nokia Shanghai Bell |
| R1-2312319 |
Summary #1 on 8.13.1 Coverage enhancement for NR NTN |
Moderator (NTT DOCOMO, INC.) |
| R1-2312320 |
Summary #2 on 8.13.1 Coverage enhancement for NR NTN |
Moderator (NTT DOCOMO, INC.) |
| R1-2312321 |
Summary #3 on 8.13.1 Coverage enhancement for NR NTN |
Moderator (NTT DOCOMO, INC.) |
| R1-2312672 |
Summary #EOM on 8.13.1 Coverage enhancement for NR NTN |
Moderator (NTT DOCOMO, INC.) |
| 8.13.2 |
Network verified UE location for NR NTN |
|
| R1-2310875 |
Maintenance of network-verified UE location for NR NTN |
Huawei, HiSilicon |
| R1-2310935 |
Maintenance on network verified UE location in NR NTN |
THALES |
| R1-2310937 |
Feature Lead Summary #1 on Network verified UE location for NR NTN |
Moderator (THALES) |
| R1-2310938 |
Feature Lead Summary #2 on Network verified UE location for NR NTN |
Moderator (THALES) |
| R1-2310939 |
Feature Lead Summary #3 on Network verified UE location for NR NTN |
Moderator (THALES) |
| R1-2311113 |
Discussions on remaining issues of UE location verification in NR NTN |
vivo |
| R1-2311201 |
Remaining issue on network verified UE location |
ZTE |
| R1-2311246 |
Discussion on remaining issue for network verified UE location for NR NTN |
OPPO |
| R1-2311325 |
Remaining issue on network verified UE location |
CATT |
| R1-2311521 |
Maintenance on Network-verified UE location for NR-NTN |
PANASONIC |
| R1-2311638 |
Remaining issue on Network verified UE location for NR NTN |
NTT DOCOMO, INC. |
| R1-2311701 |
On Remaining Issues of Network Verified UE Location |
Apple |
| R1-2311759 |
Remaining Issues on Network Verified UE Location for NR NTN |
ETRI |
| R1-2311862 |
Remaining issues on network verified UE location for NR NTN |
Samsung |
| R1-2311942 |
On maintenance of network verified UE location for NR NTN |
Ericsson Inc. |
| R1-2311995 |
Network verified UE location for NR NTN |
MediaTek Inc. |
| R1-2312053 |
Maintenance on network verified UE location for NR NTN |
Qualcomm Incorporated |
| R1-2312138 |
Remaining open issues related to network verified UE location for NR over NTN |
Nokia, Nokia Shanghai Bell |
| R1-2312258 |
Network verified UE location for NR NTN |
MediaTek Inc. |
| 8.13.3 |
Disabling of HARQ feedback for IoT NTN |
|
| R1-2310878 |
Maintenance of disabling of HARQ feedback for IoT NTN |
Huawei, HiSilicon |
| R1-2310965 |
Maintenance on disabling HARQ feedback for IoT NTN |
Ericsson |
| R1-2311180 |
Remaining issues on disabling of HARQ feedback for IoT NTN |
Spreadtrum Communications |
| R1-2311202 |
Remaining issue on disabling of HARQ feedback |
ZTE |
| R1-2311247 |
Discussion on remaining issue on disabling of HARQ feedback for IoT NTN |
OPPO |
| R1-2311654 |
Maintenance on disabling of HARQ feedback for IoT NTN |
Nokia, Nokia Shanghai Bell |
| R1-2311702 |
On Higher Layer Signaling for HARQ Feedback Disabling for IoT NTN |
Apple |
| R1-2311728 |
Disabling of HARQ feedback for IoT NTN |
Lenovo |
| R1-2311998 |
Remaining issues of disabling of HARQ feedback for IoT NTN |
MediaTek Inc. |
| R1-2312388 |
FLS#1 on disabling of HARQ feedback for IoT NTN |
Moderator (Lenovo) |
| R1-2312389 |
FLS#2 on disabling of HARQ feedback for IoT NTN |
Moderator (Lenovo) |
| R1-2312460 |
FLS#3 on disabling of HARQ feedback for IoT NTN |
Moderator(Lenovo) |
| 8.13.4 |
Improved GNSS operations for IoT NTN |
|
| R1-2310879 |
Maintenance of improved GNSS operations for IoT NTN |
Huawei, HiSilicon |
| R1-2311181 |
Remaining issues on improved GNSS operations for IoT NTN |
Spreadtrum Communications |
| R1-2311203 |
Remaining issue on improved GNSS operation |
ZTE |
| R1-2311248 |
Discussion on remaining issue for improved GNSS operation for IoT NTN |
OPPO |
| R1-2311512 |
Remaining issues on Improved GNSS Operations for IoT NTN |
NEC |
| R1-2311586 |
Discussion on the remaining issues for the improved GNSS operation for IoT NTN |
Beijing Xiaomi Mobile Software |
| R1-2311655 |
Maintenance on improved GNSS operations for IoT NTN |
Nokia, Nokia Shanghai Bell |
| R1-2311703 |
Remaining issues on improved GNSS operations for IoT NTN |
Apple |
| R1-2311863 |
Remaining issues for improved GNSS operations for IoT NTN |
Samsung |
| R1-2311943 |
On maintenance of improved GNSS operations for IoT NTN |
Ericsson Inc. |
| R1-2311999 |
Remaining issues on improved GNSS operations for IoT NTN |
MediaTek Inc. |
| R1-2312054 |
Improved GNSS Operations for IoT-NTN |
Qualcomm Incorporated |
| R1-2312128 |
Improved GNSS operations for IoT NTN |
Nordic Semiconductor ASA |
| R1-2312298 |
Feature lead summary#1 of AI 8.13.4 on improved GNSS operations |
Moderator (MediaTek) |
| R1-2312299 |
Feature lead summary#2 of AI 8.13.4 on improved GNSS operations |
Moderator (MediaTek) |
| R1-2312300 |
Feature lead summary#3 of AI 8.13.4 on improved GNSS operations |
Moderator (MediaTek) |
| R1-2312656 |
Draft LS on improved GNSS operations in Rel-18 IoT NTN |
Moderator (MediaTek Inc.) |
| R1-2312657 |
LS on improved GNSS operations in Rel-18 IoT NTN |
Moderator (MediaTek Inc.) |
| R1-2312696 |
LS on improved GNSS operations in Rel-18 IoT NTN |
Moderator (MediaTek Inc.) |
| 8.14 |
Study on Artificial Intelligence (AI)/Machine Learning (ML) for NR Air Interface |
|
| R1-2310933 |
Text Proposals to TR 38.843 |
Ericsson Inc. |
| R1-2312055 |
Updated TR 38.843 including RAN1 agreements from RAN1#114bis |
Qualcomm Incorporated |
| R1-2312764 |
TR 38.843 v1.3.0 on Artificial Intelligence (AI)/Machine Learning (ML) for NR air interface |
Qualcomm |
| 8.14.1 |
General aspects of AI/ML framework |
|
| R1-2310818 |
Discussion on remaining open issues of AI/ML for air-interface general framework |
FUTUREWEI |
| R1-2310844 |
Remaining issues on general aspects of AI/ML framework |
Huawei, HiSilicon |
| R1-2310977 |
Discussion on general aspects of AI/ML framework |
Continental Automotive |
| R1-2310987 |
Discussion on general aspects of common AI PHY framework |
ZTE |
| R1-2310999 |
Discussion on remaining issues of AI/ML general framework |
Ericsson |
| R1-2311047 |
Discussion on general aspects of AI/ML framework |
Fujitsu |
| R1-2311114 |
Discussions on AI/ML framework |
vivo |
| R1-2311151 |
General aspects of AI/ML framework for NR air interface |
Intel Corporation |
| R1-2311182 |
Discussion on general aspects of AIML framework |
Spreadtrum Communications |
| R1-2311269 |
On general aspects of AI/ML framework |
OPPO |
| R1-2311326 |
General aspects of AI/ML framework |
CATT |
| R1-2311390 |
Discussion on the remaining issues of AI/ML framework |
xiaomi |
| R1-2311423 |
Discussion on general aspects of AI ML framework |
NEC |
| R1-2311436 |
Remaining issues on AI/ML framework |
LG Electronics |
| R1-2311449 |
Remaining issues on general aspects of AI/ML framework |
Panasonic |
| R1-2311499 |
Discussion on general aspects of AI/ML framework |
CMCC |
| R1-2311527 |
Remaining issues on general AI/ML framework |
Sony |
| R1-2311529 |
General aspects of AI and ML framework for NR air interface |
NVIDIA |
| R1-2311539 |
Remaining details on general aspects of AI/ML framework |
InterDigital, Inc. |
| R1-2311572 |
On General Aspects of AI/ML Framework |
Google |
| R1-2311639 |
Discussion on general aspects of AI/ML framework |
NTT DOCOMO, INC. |
| R1-2311704 |
Discussion on general aspect of AI/ML framework |
Apple |
| R1-2311760 |
Discussion on general aspects of AI_ML framework for NR air interface |
ETRI |
| R1-2311783 |
Remaining Issues on General Aspects of AI/ML |
Nokia, Nokia Shanghai Bell |
| R1-2311864 |
Views on the remaining general aspects of AI/ML framework |
Samsung |
| R1-2311888 |
Discussion on general aspects of AI/ML framework |
Sharp |
| R1-2311908 |
Remaining issues on general aspects of AI/ML framework |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2311936 |
Remaining issues on general aspects of AI/ML framework |
Ruijie Network Co. Ltd |
| R1-2311940 |
On general aspects of AI/ML framework |
Lenovo |
| R1-2312056 |
General aspects of AI-ML framework |
Qualcomm Incorporated |
| R1-2312087 |
General Aspects of AI/ML framework |
AT&T |
| R1-2312090 |
General aspects of AI/ML framework for NR air interface |
Baicells |
| R1-2312106 |
Discussions on General Aspects of AI/ML Framework |
Indian Institute of Tech (M), IIT Kanpur |
| R1-2312120 |
Discussions on General Aspects of AI_ML Framework |
IIT Kanpur, Indian Institute of Technology Madras (IITM) |
| R1-2312174 |
Prediction of untransmitted beams in a UE-side AI-ML model |
Rakuten Symphony |
| R1-2312402 |
Summary#1 of General Aspects of AI/ML Framework |
Moderator (Qualcomm) |
| R1-2312403 |
Summary#2 of General Aspects of AI/ML Framework |
Moderator (Qualcomm) |
| R1-2312404 |
Summary#3 of General Aspects of AI/ML Framework |
Moderator (Qualcomm) |
| R1-2312405 |
Summary#4 of General Aspects of AI/ML Framework |
Moderator (Qualcomm) |
| R1-2312406 |
Summary#5 of General Aspects of AI/ML Framework |
Moderator (Qualcomm) |
| R1-2312407 |
Final summary of General Aspects of AI/ML Framework |
Moderator (Qualcomm) |
| R1-2312408 |
Draft Reply LS on AI/ML Core Network enhancements |
Moderator (Qualcomm) |
| 8.14.2 |
Other aspects on AI/ML for CSI feedback enhancement |
|
| R1-2310819 |
Discussion on remaining open issues for other aspects of AI/ML for CSI feedback enhancement |
FUTUREWEI |
| R1-2310845 |
Remaining issues on AI/ML for CSI feedback enhancement |
Huawei, HiSilicon |
| R1-2310914 |
Discussions on AI-CSI |
Ericsson |
| R1-2310984 |
Remaining issues discussion on other aspects of AI/ML for CSI feedback enhancement |
SEU |
| R1-2310988 |
Discussion on other aspects for AI CSI feedback enhancement |
ZTE |
| R1-2311048 |
Views on specification impact for CSI feedback enhancement |
Fujitsu |
| R1-2311115 |
Other aspects on AI/ML for CSI feedback enhancement |
vivo |
| R1-2311149 |
Discussion on AI/ML for CSI feedback |
Intel Corporation |
| R1-2311183 |
Discussion on other aspects on AIML for CSI feedback |
Spreadtrum Communications |
| R1-2311270 |
On other aspects of AI/ML for CSI feedback enhancement |
OPPO |
| R1-2311327 |
Other aspects for AI/ML CSI feedback enhancement |
CATT |
| R1-2311391 |
Remaining issues on specification impact for CSI feedback based on AI/ML |
xiaomi |
| R1-2311415 |
Other aspects on AI/ML for CSI feedback enhancement |
NEC |
| R1-2311437 |
Remaining issues on AI/ML for CSI enhancement |
LG Electronics |
| R1-2311446 |
Discussion on AI/ML for CSI feedback enhancement |
Panasonic |
| R1-2311500 |
Discussion on other aspects on AI/ML for CSI feedback enhancement |
CMCC |
| R1-2311528 |
Remaining issues on CSI measurement enhancements via AI/ML |
Sony |
| R1-2311530 |
AI and ML for CSI feedback enhancement |
NVIDIA |
| R1-2311540 |
Remaining details on other aspects for CSI feedback enhancement |
InterDigital, Inc. |
| R1-2311554 |
Discussion on AI/ML for CSI feedback enhancement |
China Telecom |
| R1-2311573 |
On Enhancement of AI/ML based CSI |
Google |
| R1-2311640 |
Discussion on AI/ML for CSI feedback enhancement |
NTT DOCOMO, INC. |
| R1-2311705 |
Discussion on other aspects of CSI others |
Apple |
| R1-2311784 |
Other aspects on AI/ML for CSI feedback enhancement |
Nokia, Nokia Shanghai Bell |
| R1-2311865 |
Views on remaining aspects on AI/ML for CSI feedback enhancement |
Samsung |
| R1-2311941 |
Further aspects of AI/ML for CSI feedback |
Lenovo |
| R1-2311992 |
Other aspects on AI/ML for CSI Feedback Enhancement |
MediaTek Inc. |
| R1-2311993 |
Other aspects on AI/ML for CSI Feedback Enhancement |
MediaTek Inc. |
| R1-2312057 |
Other aspects on AI/ML for CSI feedback enhancement |
Qualcomm Incorporated |
| R1-2312088 |
Discussion on AI/ML for CSI feedback enhancement |
AT&T |
| R1-2312107 |
Discussions on Other Aspects on AI/ML for CSI Feedback Enhancement |
Indian Institute of Tech (M), IIT Kanpur |
| R1-2312129 |
Other aspects on AI/ML for CSI feedback enhancement |
ITL |
| R1-2312173 |
Varying CSI feedback granularity based on channel conditions |
Rakuten Symphony |
| R1-2312333 |
Summary #1 on other aspects of AI/ML for CSI enhancement |
Moderator (Apple) |
| R1-2312334 |
Summary #2 on other aspects of AI/ML for CSI enhancement |
Moderator (Apple) |
| R1-2312335 |
Summary #3 on other aspects of AI/ML for CSI enhancement |
Moderator (Apple) |
| R1-2312336 |
Summary #4 on other aspects of AI/ML for CSI enhancement |
Moderator (Apple) |
| R1-2312337 |
Final summary on other aspects of AI/ML for CSI enhancement |
Moderator (Apple) |
| 8.14.3 |
Remaining aspects on AI/ML |
|
| R1-2310846 |
Highlights for the evaluation on AI/ML based CSI feedback enhancement |
Huawei, HiSilicon |
| R1-2310906 |
Remaining Aspects of AI/ML for Positioning Accuracy Enhancement |
Ericsson |
| R1-2311194 |
Remaining open aspects of AI/ML positioning |
Moderator (vivo) |
| R1-2311271 |
Other aspects on AI/ML for beam management |
OPPO |
| R1-2311866 |
Remaining aspects for evaluation of AI/ML for beam management |
Moderator (Samsung) |
| R1-2312383 |
Summary#1 for other aspects on AI/ML for beam management |
Moderator (OPPO) |
| R1-2312384 |
Summary#2 for other aspects on AI/ML for beam management |
Moderator (OPPO) |
| R1-2312399 |
Summary#1 for CSI evaluation of [115-R18-AI/ML] |
Moderator (Huawei) |
| R1-2312400 |
Summary#2 for CSI evaluation of [115-R18-AI/ML] |
Moderator (Huawei) |
| R1-2312401 |
Summary#3 for CSI evaluation of [115-R18-AI/ML] |
Moderator (Huawei) |
| R1-2312413 |
Summary #1 on Remaining Aspects of Evaluating AI/ML for Positioning Accuracy Enhancement |
Moderator (Ericsson) |
| R1-2312414 |
Summary #2 on Remaining Aspects of Evaluating AI/ML for Positioning Accuracy Enhancement |
Moderator (Ericsson) |
| R1-2312415 |
Summary #3 on Remaining Aspects of Evaluating AI/ML for Positioning Accuracy Enhancement |
Moderator (Ericsson) |
| R1-2312425 |
FL summary #1 on remaining open aspects of AI/ML positioning |
Moderator (vivo) |
| R1-2312445 |
FL summary #1 for remaining aspects for evaluation of AI/ML for beam management |
Moderator (Samsung) |
| R1-2312515 |
Summary #4 on Remaining Aspects of Evaluating AI/ML for Positioning Accuracy Enhancement |
Moderator (Ericsson) |
| R1-2312516 |
Summary #5 on Remaining Aspects of Evaluating AI/ML for Positioning Accuracy Enhancement |
Moderator (Ericsson) |
| R1-2312560 |
FL summary #2 for remaining aspects for evaluation of AI/ML for beam management |
Moderator (Samsung) |
| R1-2312603 |
Summary#4 for CSI evaluation of [115-R18-AI/ML] |
Moderator (Huawei) |
| R1-2312604 |
TP on CSI evaluation for TR38.843 |
Moderator (Huawei) |
| 8.15 |
Study on Self-Evaluation towards the IMT-2020 Submission of the 3GPP Satellite Radio Interface Technology |
|
| R1-2312001 |
Text Proposal to TR 37.911 for Connection Density evaluation for IoT NTN and NR NTN |
MediaTek, THALES, Qualcomm |
| R1-2312175 |
[Draft] Reply LS on RAN2 progress of NTN Self Evaluation |
Ericsson |
| R1-2312444 |
Text Proposal to TR 37.911 for Connection Density evaluation for IoT NTN and NR NTN |
MediaTek, THALES, Qualcomm |
| R1-2312511 |
Session notes for 8.15 (Study on Self-Evaluation towards the 3GPP submission of a IMT-2020 Satellite Radio Interface Technology) |
Ad-Hoc Chair (Huawei) |
| 8.15.1 |
Evaluation methodology |
|
| R1-2311204 |
Discussion on the evaluation methodology of the self-evaluation |
ZTE |
| R1-2311257 |
Discussion on self-evaluation methodology for IMT-2020 satellite radio interface |
OPPO |
| R1-2312058 |
Further discussion on self-evaluation assumptions |
Qualcomm Incorporated |
| R1-2312139 |
On evaluation criteria for adopting the evaluation results for TR 37.911 |
Nokia, Nokia Shanghai Bell |
| R1-2312149 |
Evaluation methodology of IMT-2020 satellite |
Huawei, HiSilicon |
| R1-2312355 |
Feature lead summary on Evaluation Methodology for IMT-2020 satellite |
Moderator (Qualcomm Incorporated) |
| 8.15.2 |
Self-evaluation results for NR NTN |
|
| R1-2310856 |
Self-evaluation results for NR NTN |
Huawei, HiSilicon |
| R1-2310940 |
Self-evaluation results for NR NTN |
THALES |
| R1-2310941 |
Feature Lead Summary#1 on self-evaluation results for NR NTN |
Moderator (THALES) |
| R1-2310942 |
Feature Lead Summary#2 on self-evaluation results for NR NTN |
Moderator (THALES) |
| R1-2311116 |
Discussions on self-evaluation results for NR NTN |
vivo |
| R1-2311205 |
Discussion on the Self-evaluation results for NR NTN |
ZTE |
| R1-2311258 |
Self-evaluation results for NR NTN |
OPPO |
| R1-2311562 |
Evaluation results of NR-NTN for IMT-2020 satellite radio interface technology |
Panasonic |
| R1-2311566 |
Self-evaluation results for NR NTN |
Beijing Xiaomi Mobile Software |
| R1-2311641 |
Self-evaluation results for NR NTN |
NTT DOCOMO, INC. |
| R1-2311750 |
Self-evaluation results for NR NTN |
CCU, ITRI |
| R1-2312059 |
Self-evaluation results for NR NTN |
Qualcomm Incorporated |
| R1-2312140 |
Comparison results related to IMT-2020 Satellite for NR over NTN for Earth Fixed Cell Vs. Earth Moving Cell |
Nokia, Nokia Shanghai Bell |
| R1-2312162 |
Satellite IMT-2020 self-evaluation results for NR NTN |
Ericsson |
| R1-2312265 |
Self-evaluation results for NR NTN |
Qualcomm Incorporated |
| R1-2312322 |
Self-evaluation results for NR NTN |
NTT DOCOMO, INC. |
| R1-2312447 |
Further evaluation results for NR NTN |
CATT |
| 8.15.3 |
Self-evaluation results for IoT NTN |
|
| R1-2311206 |
Discussion on the Self-evaluation results for IoT NTN |
ZTE |
| R1-2311259 |
Self-evaluation results for IoT NTN |
OPPO |
| R1-2312002 |
Evaluation results for IoT NTN Connection Density |
MediaTek Inc. |
| R1-2312060 |
Self-evaluation results for IOT NTN |
Qualcomm Incorporated |
| R1-2312150 |
Self-evaluation results for IoT NTN |
Huawei, HiSilicon |
| R1-2312419 |
Feature Lead summary for 8.15.3: Self-Evaluation Results for IoT NTN |
Moderator (MediaTek) |
| 8.16 |
UE Features |
|
| R1-2312569 |
Updated RAN1 UE features list for Rel-18 LTE after RAN1#115 |
Moderators (AT&T, NTT DOCOMO, INC.) |
| R1-2312570 |
Draft LS on Rel-18 RAN1 UE features list for LTE after RAN1#115 |
Moderators (AT&T, NTT DOCOMO, INC.) |
| R1-2312571 |
LS on Rel-18 RAN1 UE features list for LTE after RAN1#115 |
RAN1, AT&T, NTT DOCOMO, INC. |
| R1-2312572 |
Updated RAN1 UE features list for Rel-18 NR after RAN1#115 |
Moderators (AT&T, NTT DOCOMO, INC.) |
| R1-2312573 |
Draft LS on Rel-18 RAN1 UE features list for NR after RAN1#115 |
Moderators (AT&T, NTT DOCOMO, INC.) |
| R1-2312574 |
LS on Rel-18 RAN1 UE features list for NR after RAN1#115 |
RAN1, AT&T, NTT DOCOMO, INC. |
| R1-2312705 |
Corrected RAN1 UE features list for Rel-18 NR after RAN1#115 |
Moderators (AT&T, NTT DOCOMO, INC.) |
| R1-2312706 |
Draft LS on updates to the Rel-18 RAN1 UE features list for NR after RAN1#115 |
Moderators (AT&T, NTT DOCOMO, INC.) |
| R1-2312707 |
LS on updates of the Rel-18 RAN1 UE features list for NR after RAN1#115 |
RAN1, AT&T, NTT DOCOMO, INC. |
| 8.16.1 |
UE features for NR MIMO evolution |
|
| R1-2310889 |
On UE features for Rel. 18 MIMO evolution WI |
Nokia, Nokia Shanghai Bell |
| R1-2310907 |
Discussion on UE features for Rel18 MIMO |
Ericsson |
| R1-2310956 |
Discussion on UE features for NR MIMO evolution |
ZTE |
| R1-2311049 |
Discussion on UE features for NR MIMO evolution |
Fujitsu |
| R1-2311117 |
Discussion on Rel-18 MIMO UE features |
vivo |
| R1-2311150 |
UE features for NR-MIMO evolution |
Intel Corporation |
| R1-2311220 |
UE features for Rel-18 MIMO evolution |
OPPO |
| R1-2311328 |
Further discussion on UE features for NR MIMO evolution |
CATT |
| R1-2311392 |
Further discussion on UE features for NR MIMO evolution |
xiaomi |
| R1-2311438 |
Discussion on Rel-18 MIMO UE features |
LG Electronics |
| R1-2311501 |
Discussion on UE features for NR MIMO evolution |
CMCC |
| R1-2311576 |
UE feature on NR MIMO evolution |
Google |
| R1-2311642 |
Discussion on UE features for NR MIMO evolution |
NTT DOCOMO, INC. |
| R1-2311706 |
Views on UE features for Rel-18 NR MIMO evolution |
Apple |
| R1-2311867 |
UE features for Rel-18 MIMO |
Samsung |
| R1-2311974 |
UE Features for NR MIMO Evolution |
MediaTek Inc. |
| R1-2312061 |
UE features for NR MIMO evolution |
Qualcomm Incorporated |
| R1-2312079 |
Summary of UE features for NR MIMO evolution |
Moderator (AT&T) |
| R1-2312152 |
UE features for NR MIMO evolution |
Huawei, HiSilicon |
| R1-2312608 |
Session Notes of AI 8.16.1 |
Ad-Hoc Chair (AT&T) |
| 8.16.2 |
UE features for NR sidelink evolution |
|
| R1-2310825 |
Sidelink unlicensed UE features |
FUTUREWEI |
| R1-2310855 |
UE features for NR sidelink evolution |
Huawei, HiSilicon |
| R1-2310890 |
On UE features for NR sidelink evolution |
Nokia, Nokia Shanghai Bell |
| R1-2311118 |
Discussion on Rel-18 sidelink UE features |
vivo |
| R1-2311184 |
Discussion on UE features for NR sidelink evolution |
Spreadtrum Communications |
| R1-2311278 |
UE features list for Rel-18 NR sidelink evolution WI |
OPPO, Huawei, HiSilicon, LG Electronics |
| R1-2311329 |
Further discussion on UE features for NR sidelink evolution |
CATT, CICTCI |
| R1-2311394 |
Discussion on UE features for NR sidelink evolution |
xiaomi |
| R1-2311519 |
Discussion on UE features for NR sidelink evolution |
ZTE, Sanechips |
| R1-2311643 |
Discussion on UE features for NR SL evolution |
NTT DOCOMO, INC. |
| R1-2311707 |
Views on UE Features for Rel-18 NR Sidelink Evolution |
Apple |
| R1-2311868 |
UE features for NR sidelink evolution |
Samsung |
| R1-2311977 |
Discussion on UE feature list for NR Sidelink Evolution |
MediaTek Inc. |
| R1-2312062 |
UE feature for sidelink evolution |
Qualcomm Incorporated |
| R1-2312575 |
Session Notes for 8.16.2 |
Ad-Hoc Chair (NTT DOCOMO) |
| R1-2312583 |
Summary on UE features for NR sidelink evolution |
Moderator (NTT DOCOMO) |
| 8.16.3 |
UE features for expanded and improved NR positioning |
|
| R1-2310826 |
Sidelink positioning UE features |
FUTUREWEI |
| R1-2310843 |
UE features for Rel-18 positioning |
Huawei, HiSilicon |
| R1-2310891 |
On UE features for expanded and improved NR positioning |
Nokia, Nokia Shanghai Bell |
| R1-2311119 |
Discussion on Rel-18 positioning UE features |
vivo |
| R1-2311147 |
On UE features for expanded and improved NR positioning |
Intel Corporation |
| R1-2311185 |
Discussion on UE features for expanded and improved NR positioning |
Spreadtrum Communications |
| R1-2311277 |
Discussion on UE features for expanded and improved NR positioning |
OPPO |
| R1-2311330 |
Remaining issues on UE features for expanded and improved NR positioning |
CATT |
| R1-2311395 |
Discussion on UE features for expanded and improved NR positioning |
xiaomi |
| R1-2311463 |
UE features for Rel-18 NR positioning |
ZTE |
| R1-2311502 |
Discussion on UE features for expanded and improved NR positioning |
CMCC |
| R1-2311555 |
Discussion on UE features for Rel-18 NR positioning |
China Telecom |
| R1-2311644 |
Discussion on UE features for expanded and improved NR positioning |
NTT DOCOMO, INC. |
| R1-2311708 |
On UE features for expanded and improved NR positioning |
Apple |
| R1-2311869 |
UE features for expanded and improved NR positioning |
Samsung |
| R1-2312063 |
UE features for expanded and improved NR positioning |
Qualcomm Incorporated |
| R1-2312080 |
Summary of UE features for expanded and improved NR positioning |
Moderator (AT&T) |
| R1-2312192 |
UE features for expanded and improved NR positioning |
Ericsson |
| R1-2312609 |
Session Notes of AI 8.16.3 |
Ad-Hoc Chair (AT&T) |
| 8.16.4 |
UE features for eRedCap |
|
| R1-2310821 |
R18 RedCap UE features |
FUTUREWEI |
| R1-2310858 |
UE features for Rel-18 RedCap |
Huawei, HiSilicon |
| R1-2310892 |
On UE features for eRedCap |
Nokia, Nokia Shanghai Bell |
| R1-2310996 |
Discussion on UE features for eRedcap |
ZTE, Sanechips |
| R1-2311120 |
Discussion on Rel-18 eRedCap UE features |
vivo |
| R1-2311186 |
Discussion on UE features for eRedCap |
Spreadtrum Communications |
| R1-2311266 |
Rel-18 eRedCap UE features |
OPPO |
| R1-2311331 |
Discussion on UE features for R18 RedCap |
CATT |
| R1-2311396 |
Discussion on UE features for eRedCap |
xiaomi |
| R1-2311428 |
Discussion on the UE features for NR NTN enhancements |
NEC |
| R1-2311556 |
Discussion on UE features for eRedCap |
China Telecom |
| R1-2311645 |
Discussion on UE features for eRedCap |
NTT DOCOMO, INC. |
| R1-2311709 |
UE features for eRedCap |
Apple |
| R1-2311870 |
UE features for eRedCap |
Samsung |
| R1-2311979 |
UE features for eRedCap |
MediaTek Inc. |
| R1-2312064 |
UE features for eRedcap |
Qualcomm Incorporated |
| R1-2312168 |
UE features for eRedCap |
Ericsson |
| R1-2312576 |
Session Notes for 8.16.4 |
Ad-Hoc Chair (NTT DOCOMO) |
| R1-2312584 |
Summary on UE features for eRedCap |
Moderator (NTT DOCOMO) |
| 8.16.5 |
UE features for NR network energy savings |
|
| R1-2310865 |
UE features for Rel-18 NES |
Huawei, HiSilicon |
| R1-2310893 |
On UE features for NR network energy savings |
Nokia, Nokia Shanghai Bell |
| R1-2310997 |
Discussion on UE features for NES |
ZTE, Sanechips |
| R1-2311050 |
UE features for Rel-18 network energy savings |
Fujitsu |
| R1-2311121 |
Discussions on UE features for network energy saving |
vivo |
| R1-2311139 |
Discussion on UE features for NES |
Intel Corporation |
| R1-2311254 |
Discussion on UE features for NR network energy savings |
OPPO |
| R1-2311332 |
Discussion on Rel-18 UE features for Network Energy Saving |
CATT |
| R1-2311397 |
Views on Rel-18 network energy saving UE features |
xiaomi |
| R1-2311503 |
Discussion on UE features for network energy saving |
CMCC |
| R1-2311557 |
Discussion on UE features for NES |
China Telecom |
| R1-2311577 |
UE feature on Network Energy Saving |
Google |
| R1-2311646 |
Discussion on UE features for NR NW energy savings |
NTT DOCOMO, INC. |
| R1-2311710 |
Views on UE features for NR Network Energy Savings |
Apple |
| R1-2311782 |
UE Features for Cell DTX/DRX |
Vodafone, Deutsche Telekom |
| R1-2311871 |
UE features for NR network energy savings |
Samsung |
| R1-2311901 |
Discussion on UE features for NES |
LG Electronics |
| R1-2311982 |
On UE features for NR network energy savings |
MediaTek Inc. |
| R1-2312065 |
UE features for NES |
Qualcomm Incorporated |
| R1-2312081 |
Summary of UE features for NR network energy savings |
Moderator (AT&T) |
| R1-2312103 |
UE features for Rel-18 network energy savings |
Ericsson |
| R1-2312610 |
Session Notes of AI 8.16.5 |
Ad-Hoc Chair (AT&T) |
| 8.16.6 |
UE features for XR enhancements |
|
| R1-2310847 |
UE features for XR enhancements |
Huawei, HiSilicon |
| R1-2310894 |
On UE features for XR enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2310998 |
Discussion on UE features for XR enhancements |
ZTE, Sanechips |
| R1-2311122 |
Discussion on Rel-18 XR UE features |
vivo |
| R1-2311187 |
Discussion on UE features for XR Enhancements |
Spreadtrum Communications |
| R1-2311280 |
Discussion on UE features for XR |
OPPO |
| R1-2311333 |
Discussion on Rel-18 UE features for XR in RAN1 |
CATT |
| R1-2311398 |
Discussion on UE features for XR-specific capacity enhancements |
xiaomi |
| R1-2311534 |
Discussion on UE features for XR |
InterDigital, Inc. |
| R1-2311647 |
Discussion on UE features for Rel-18 XR enhancements |
NTT DOCOMO, INC. |
| R1-2311711 |
Views on UE features for XR enhancements |
Apple |
| R1-2311872 |
UE features for XR |
Samsung |
| R1-2311902 |
Discussion on UE features for XR enhancements |
LG Electronics |
| R1-2311906 |
On UE features for XR Enhancements |
Ericsson |
| R1-2311983 |
Discussion on UE features for XR enhancements |
MediaTek Inc. |
| R1-2312066 |
UE features for XR enhancements |
Qualcomm Incorporated |
| R1-2312577 |
Session Notes for 8.16.6 |
Ad-Hoc Chair (NTT DOCOMO) |
| R1-2312585 |
Summary on UE features for XR enhancements |
Moderator (NTT DOCOMO) |
| 8.16.7 |
UE features for NR mobility enhancements |
|
| R1-2310850 |
UE features on R18 Mobility Enhancement |
Huawei, HiSilicon |
| R1-2310895 |
On UE features for NR mobility enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2310957 |
Discussion on UE features for NR mobility enhancements |
ZTE |
| R1-2311033 |
UE-features for NR mobility enhancements |
Ericsson |
| R1-2311123 |
Discussion on UE features for L1/L2-triggered Mobility |
vivo |
| R1-2311188 |
Discussion on UE features for mobility |
Spreadtrum Communications |
| R1-2311232 |
Discussion on UE features for NR mobility enhancements |
OPPO |
| R1-2311504 |
Discussion on the UE features for NR Mobility |
CMCC |
| R1-2311648 |
Discussion on UE features for NR mobility enhancements |
NTT DOCOMO, INC. |
| R1-2311712 |
UE features for NR mobility enhancements |
Apple |
| R1-2311873 |
UE features for mobility |
Samsung |
| R1-2311985 |
Views on UE features for NR mobility enhancements |
MediaTek Inc. |
| R1-2312067 |
UE features for NR mobility enhancements |
Qualcomm Incorporated |
| R1-2312084 |
Summary of UE features for NR mobility enhancements |
Moderator (AT&T) |
| R1-2312613 |
Session Notes of AI 8.16.7 |
Ad-Hoc Chair (AT&T) |
| 8.16.8 |
UE features for coverage enhancements |
|
| R1-2310885 |
UE features for Coverage Enhancement |
Huawei, HiSilicon |
| R1-2310896 |
On UE features for coverage enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2311026 |
Discussion on UE feature for coverage enhancements |
ZTE |
| R1-2311124 |
Discussions on Rel-18 NR coverage enhancements UE features |
vivo |
| R1-2311136 |
Discussion on UE features for NR coverage enhancement |
Intel Corporation |
| R1-2311189 |
Discussion on UE features for coverage enhancements |
Spreadtrum Communications |
| R1-2311267 |
Rel-18 UE features for coverage enhancements |
OPPO |
| R1-2311334 |
UE features for coverage enhancements |
CATT |
| R1-2311399 |
Discussion on UE features for coverage enhancements |
xiaomi |
| R1-2311447 |
Discussion on UE features for further NR coverage enhancement in Rel.18 |
Panasonic |
| R1-2311505 |
Discussion on UE feature for coverage enhancement |
CMCC |
| R1-2311558 |
Discussion on UE features for coverage enhancement |
China Telecom |
| R1-2311649 |
Discussion on UE features for NR further coverage enhancements |
NTT DOCOMO, INC. |
| R1-2311713 |
Views on UE features for NR coverage ehancmenents |
Apple |
| R1-2311774 |
UE features for Rel-18 Coverage Enhancements |
Sharp |
| R1-2311874 |
UE features for coverage enhancements |
Samsung |
| R1-2311948 |
UE Features for Coverage Enhancements |
Ericsson |
| R1-2311987 |
Discussion on UE features for coverage enhancements |
MediaTek Inc. |
| R1-2312068 |
UE features for coverage enhancements |
Qualcomm Incorporated |
| R1-2312578 |
Session Notes for 8.16.8 |
Ad-Hoc Chair (NTT DOCOMO) |
| R1-2312586 |
Summary on UE features for coverage enhancements |
Moderator (NTT DOCOMO) |
| 8.16.9 |
UE features for dedicated spectrum less than 5MHz |
|
| R1-2310822 |
Less than 5 MHz dedicated spectrum UE features |
FUTUREWEI |
| R1-2310859 |
UE features for dedicated spectrum less than 5 MHz |
Huawei, HiSilicon |
| R1-2310897 |
On UE features for dedicated spectrum less than 5MHz |
Nokia, Nokia Shanghai Bell |
| R1-2310968 |
On UE features for LessThan5MHzFR1 |
Ericsson |
| R1-2311027 |
Discussion on UE feature for dedicated spectrum less than 5MHz |
ZTE |
| R1-2311335 |
UE features for dedicated spectrum less than 5MHz |
CATT |
| R1-2311650 |
Discussion on UE features for dedicated spectrum less than 5MHz |
NTT DOCOMO, INC. |
| R1-2311875 |
UE features for dedicated spectrum less than 5MHz |
Samsung |
| R1-2311989 |
UE features for dedicated spectrum less than 5MHz |
MediaTek Inc. |
| R1-2312069 |
UE features for dedicated spectrum less than 5MHz |
Qualcomm Incorporated |
| R1-2312579 |
Session Notes for 8.16.9 |
Ad-Hoc Chair (NTT DOCOMO) |
| R1-2312587 |
Summary on UE features for dedicated spectrum less than 5MHz |
Moderator (NTT DOCOMO) |
| 8.16.10 |
UE features for eDSS |
|
| R1-2310898 |
On UE features for eDSS |
Nokia, Nokia Shanghai Bell |
| R1-2311190 |
Discussion on UE features for eDSS |
Spreadtrum Communications |
| R1-2312153 |
UE features for eDSS |
Huawei, HiSilicon |
| R1-2312580 |
Session Notes for 8.16.10 |
Ad-Hoc Chair (NTT DOCOMO) |
| R1-2312588 |
Summary on UE features for eDSS |
Moderator (NTT DOCOMO) |
| 8.16.11 |
UE features for NR NCR |
|
| R1-2310862 |
UE features for NR NCR |
Huawei, HiSilicon |
| R1-2310899 |
On UE features for NR NCR |
Nokia, Nokia Shanghai Bell |
| R1-2311032 |
UE-features for NR NCR |
Ericsson |
| R1-2311761 |
Discussion on NCR features |
ETRI |
| R1-2311876 |
UE feature for NR NCR |
Samsung |
| R1-2312082 |
Summary of UE features for NR NCR |
Moderator (AT&T) |
| R1-2312611 |
Session Notes of AI 8.16.11 |
Ad-Hoc Chair (AT&T) |
| 8.16.12 |
UE features for MC enhancements |
|
| R1-2310886 |
Discussion on UE features for MC enhancements |
Huawei, HiSilicon |
| R1-2310900 |
On UE features for MC enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2311028 |
Discussion on UE feature for MC enhancements |
ZTE |
| R1-2311125 |
Discussion on Rel-18 Multi-carrier enhancements UE features |
vivo |
| R1-2311191 |
Discussion on UE features for multi-carrier enhancement |
Spreadtrum Communications |
| R1-2311279 |
Discussion on UE features for multi-carrier enhancement |
OPPO |
| R1-2311393 |
Discussion on UE features for MC enhancements |
xiaomi |
| R1-2311651 |
Discussion on UE features for Multi-carrier enhancements |
NTT DOCOMO, INC. |
| R1-2311714 |
Views on UE features for Rel-18 MC enhancements |
Apple |
| R1-2311877 |
UE features for multi-carrier enhancements |
Samsung |
| R1-2311903 |
Discussion on UE features for MC enhancements |
LG Electronics |
| R1-2311991 |
On UE feature discussion for Rel-18 multi-carrier enhancement |
MediaTek Inc. |
| R1-2312070 |
UE features for MC enhancements |
Qualcomm Incorporated |
| R1-2312104 |
UE features for Rel-18 multi-carrier enhancements |
Ericsson |
| R1-2312581 |
Session Notes for 8.16.12 |
Ad-Hoc Chair (NTT DOCOMO) |
| R1-2312589 |
Summary on UE features for MC enhancements |
Moderator (NTT DOCOMO) |
| 8.16.13 |
UE features for IoT NTN enhancements |
|
| R1-2310881 |
UE features for IoT NTN enhancements |
Huawei, HiSilicon |
| R1-2310901 |
On UE features for IoT NTN enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2310967 |
On UE features for IoT NTN enhancements |
Ericsson |
| R1-2311192 |
Discussion on UE features for IoT NTN enhancements |
Spreadtrum Communications |
| R1-2311207 |
Discussion on UE features for IoT-NTN |
ZTE |
| R1-2311255 |
Discussion on UE features for IoT NTN enhancements |
OPPO |
| R1-2311564 |
Discussion on the UE features for IoT NTN |
Beijing Xiaomi Mobile Software |
| R1-2311715 |
Views on UE Features for Rel-18 IoT NTN Enhancements |
Apple |
| R1-2311878 |
UE features for IoT NTN enhancements |
Samsung |
| R1-2312000 |
Views on UE features for Rel-18 IoT NTN enhancements |
MediaTek Inc. |
| R1-2312071 |
UE features for IOT NTN enhancements |
Qualcomm Incorporated |
| R1-2312085 |
Summary of UE features for IoT NTN enhancements |
Moderator (AT&T) |
| R1-2312127 |
On IoT NTN feature set |
Nordic Semiconductor ASA |
| R1-2312614 |
Session Notes of AI 8.16.13 |
Ad-Hoc Chair (AT&T) |
| 8.16.14 |
UE features for NR NTN enhancements |
|
| R1-2310880 |
UE features for NR NTN enhancements |
Huawei, HiSilicon |
| R1-2310902 |
On UE features for NR NTN enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2310915 |
On UE features for NR NTN enhancements |
Ericsson |
| R1-2311126 |
Discussions on NR NTN enhancements UE features |
vivo |
| R1-2311193 |
Discussion on UE feature of NR NTN enhancements |
Spreadtrum Communications |
| R1-2311208 |
Discussion on UE features for NR-NTN |
ZTE |
| R1-2311256 |
Discussion on UE features for NR NTN enhancements |
OPPO |
| R1-2311652 |
Discussion on UE features for NR NTN enhancements |
NTT DOCOMO, INC. |
| R1-2311716 |
Views on UE Features for Rel-18 NR NTN Enhancements |
Apple |
| R1-2311733 |
Discussion on the UE features for NR NTN |
Beijing Xiaomi Mobile Software |
| R1-2311762 |
Discussion on UE features for NR NTN enhancements |
ETRI |
| R1-2311775 |
Discussions on UE features for NR NTN |
Sharp |
| R1-2311879 |
UE features for NR NTN enhancements |
Samsung |
| R1-2311919 |
Discussions on UE features for NR NTN enhancements |
LG Electronics |
| R1-2311997 |
UE features for NR NTN enhancements |
MediaTek Inc. |
| R1-2312072 |
UE features for NR NTN enhancements |
Qualcomm Incorporated |
| R1-2312083 |
Summary of UE features for NR NTN enhancements |
Moderator (AT&T) |
| R1-2312612 |
Session Notes of AI 8.16.14 |
Ad-Hoc Chair (AT&T) |
| 8.16.15 |
UE features for BWP without restriction |
|
| R1-2310903 |
On UE features for BWP without restriction |
Nokia, Nokia Shanghai Bell |
| R1-2310974 |
UE features for BWP without restriction |
Ericsson |
| R1-2311653 |
Discussion on UE features for BWP without restriction |
NTT DOCOMO, INC. |
| R1-2311781 |
Remaining clarifications on BWP Without Restriction |
Vodafone, vivo, Nokia, Nokia Shanghai Bell |
| R1-2311880 |
UE features for BWP without restriction |
Samsung |
| R1-2312003 |
UE features for BWP without restriction |
MediaTek Inc. |
| R1-2312086 |
Summary of UE features for BWP without restriction |
Moderator (AT&T) |
| R1-2312615 |
Session Notes of AI 8.16.15 |
Ad-Hoc Chair (AT&T) |
| 8.16.16 |
Other |
|
| R1-2310904 |
On UE features for TEI18 |
Nokia, Nokia Shanghai Bell |
| R1-2311029 |
Discussion on UE feature for Rel-18 TEI |
ZTE |
| R1-2311140 |
Discussion on UE features for TEI |
Intel Corporation |
| R1-2311881 |
UE features for endorsed Rel-18 TEI |
Samsung |
| R1-2312073 |
UE features for endorsed TEI proposals. |
Qualcomm Incorporated |
| R1-2312227 |
UE features for endorsed Rel-18 TEI on HARQ multiplexing on PUSCH |
Huawei, HiSilicon |
| R1-2312244 |
On UE features for HARQ-ACK multiplexing on PUSCH TEI |
Ericsson |
| R1-2312582 |
Session Notes for 8.16.16 |
Ad-Hoc Chair (NTT DOCOMO) |
| R1-2312590 |
Summary on UE features for TEIs |
Moderator (NTT DOCOMO) |
| 8.17 |
Other |
|
| R1-2310934 |
Discussion on enhanced sidelink operation on FR2 licensed spectrum |
KRRI |
| R1-2311127 |
Maintenance for BWP without restriction |
vivo, Vodafone |
| R1-2311506 |
TP for TR 38.858 Study on Evolution of NR Duplex Operation |
CMCC, Samsung |
| R1-2311882 |
Remaining issue for HARQ-ACK multiplexing on PUSCH |
Samsung |
| R1-2312074 |
Maintenance for BWP without restriction |
Qualcomm Incorporated |
| R1-2312203 |
Correction to the Bandwidth Part without Restriction capability names |
Nokia, Nokia Shanghai Bell |
| R1-2312245 |
Discussion on HARQ-ACK multiplexing on PUSCH TEI |
Ericsson |
| R1-2312309 |
TR 38.858 v1.0.1 Study on Evolution of NR Duplex Operation |
ETSI MCC |
| R1-2312423 |
Summary #1 of discussion on multiplexing HARQ-ACK in a PUSCH |
Moderator (Samsung) |
| R1-2312429 |
TP for TR 38.858 Study on Evolution of NR Duplex Operation |
Moderator (Samsung) |
| R1-2312431 |
Draft summary of discussion on BWP Without Restriction maintenance |
Moderator (Vodafone) |
| R1-2312624 |
Summary #2 of discussion on multiplexing HARQ-ACK in a PUSCH |
Moderator (Samsung) |
| R1-2312643 |
Final summary of discussion on BWP Without Restriction maintenance |
Moderator (Vodafone) |